hi jeevan_ullas - i bet we can now. that's probably code left over from our goamz days.
jeevan_ullas
thanks phinze
michalgm joined the channel
sfeinste joined the channel
holgr joined the channel
svij_ has quit
jeevan_ullas has quit
xerxas joined the channel
Zool_
Hello terraform team!
Each terraform versions comes with more and more features but lots of changes in code structure/calls.
Is there any benefits to store version used to push the last apply in tfstate?
tmichael has quit
GriffinHeart joined the channel
because applying configuration between differents versions of terraform (ie : 3.7 and 4.2) can be dangerous
tmichael joined the channel
phinze
hi Zool_ - good question! there are two parts to consider: the state and the config
for the state, we do support something called "state migration" that allows provider authors to version the state of their resource, and convert any old copies they find.
for the config, we support both deprecation warnings and errors, which allows provider authors to inform the user about old config.
Zool_
state file migration has to be triggered? or is it running automagically in background?
phinze
these features are relatively young, but they're in and we'll continue to improve them. the key from a user standpoint is to remember that with a statefile backup, you can always safely run `terraform plan` using a new version of TF and it will tell you exactly what it wants to do
state file migration runs automatically in the background - if you enable debug logging with TF_LOG=1 and you run terraform on an old statefile you'll see messages like `Found Schema Version X, Migrating to version Y`
michalgm has left the channel
Zool_
Ok phinze thank you, I better understand how it is working now :)
GriffinHeart has quit
failshell joined the channel
phinze
no prob - you're welcome :)
Azrael has quit
Azrael joined the channel
Azrael is now known as Guest64608
failshell
glorious morning: deploying our new AWS stacks using terraform