You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am seeing differences in the plan between plan and apply stages where unused attributes show as default values (empty string, empty map, etc.) in the plan, but are hidden attributes in the plan generated during apply. As far I can tell everything is the same (Terraform version, AWS provider version - v4.29.0, my code, module inputs, etc.), except for the GitHub action being used (plan vs apply).
Is it possible the change was applied before the proper apply job was run? (assuming that the lambda package changes every time/was changed externally).
Is it possible the change was applied before the proper apply job was run? (assuming that the lambda package changes every time/was changed externally).
There are no changes being applied between the plan and apply in GitHub Actions
Problem description
I am seeing differences in the plan between plan and apply stages where unused attributes show as default values (empty string, empty map, etc.) in the plan, but are hidden attributes in the plan generated during apply. As far I can tell everything is the same (Terraform version, AWS provider version - v4.29.0, my code, module inputs, etc.), except for the GitHub action being used (plan vs apply).
pull request plan example resource:
same resource in the apply plan:
Any idea why the plan is different?
Terraform version
1.2.8
Backend
s3
Workflow YAML
No response
Workflow log
No response
The text was updated successfully, but these errors were encountered: