DevOps Community Sponsored by Cloud Posse

SweetOps

I had asked a question in <#CQCDCLA1M>: <https://sweetops.slack.com/archives/CQCDCLA1M/p1771189798862939> But it appears this is the more proper place to ask. I just realized we're running an older version of Atmos for our actions, 1.200.0. I run a more updated version locally, I can check the plan-diff with my version and see if it ignores the change if it's likely that's the issue.

It could be related, also we will have native support for  GHA in atmos coming pretty soon (without using separate actions)

<https://github.com/cloudposse/atmos/pull/1891|https://github.com/cloudposse/atmos/pull/1891>

<https://github.com/cloudposse/atmos/blob/osterman/native-ci-terraform/docs/prd/native-ci-integration.md|https://github.com/cloudposse/atmos/blob/osterman/native-ci-terraform/docs/prd/native-ci-integration.md>

Looks fantastic, thanks for pointing it out!

Just wanted to confirm that I'm seeing the same thing with 1.206.2. My test is just running an atmos terraform plan and -out=/tmp/rds.tfplan The plan show no changes. But if I wait a few minutes and run a plan-diff and give it --orig=/tmp/rds.tfplan it shows latest_restorable_time as different.

<@U0AF36NB6S2>, I recommend rolling back to the previous version of Atmos. You may not see differences because of some regression. I need to investigate. Could you pls send me the plan where I can see the latest_restorable_time? I will use this to prepare a test case for atmos plan-diff fix.
For now, I do not see that field in exceptions <https://github.com/cloudposse/atmos/blob/main/internal/exec/terraform_plan_diff_comparison.go#L406>

As a workaround, you can probably use `ignore_changes`  lifecycle block
<https://developer.hashicorp.com/terraform/language/meta-arguments/lifecycle#ignore_changes>

Hi Igor, thanks! Erik actually moved this conversation over to our enterprise channel. Sorry to have started it there, I didn't realize where it should have gone. I'll send you the info over there.