Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Show warnings even if no changes #24095

Merged
merged 2 commits into from
Feb 19, 2020

Conversation

nyurik
Copy link
Contributor

@nyurik nyurik commented Feb 13, 2020

Fixes #22541

This change will print warnings, such as deprecations,
even if plan has no changes.

Fixes hashicorp#22541

This change will print warnings, such as deprecations,
even if plan has no changes.
Copy link
Contributor

@apparentlymart apparentlymart left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for working on this @nyurik!

This does look like the right cause. Thanks for tracking that down! I left feedback inline about a slightly different approach to fixing it which I think will make this codepath easier to follow and maintain in future, while getting the same result.

backend/local/backend_plan.go Outdated Show resolved Hide resolved
@nyurik
Copy link
Contributor Author

nyurik commented Feb 19, 2020

@apparentlymart thanks, I updated the PR. Is there anything else that needs to be done here, or any specific person to ping to review it? Thanks!

@apparentlymart
Copy link
Contributor

Thanks for the updates, @nyurik! This looks good to me, and I'm going to merge it.

@apparentlymart apparentlymart merged commit 6eb9685 into hashicorp:master Feb 19, 2020
@nyurik nyurik deleted the always-show-warnings branch February 20, 2020 00:24
@nyurik
Copy link
Contributor Author

nyurik commented Feb 20, 2020

@apparentlymart would it be possible to backport this to 0.11 branch? This way it will make migration 0.11 -> 0.12 much easier -- we would simply need to migrate to the latest of the 0.11 branch, and our terraforms will instantly start showing any kind of upgrade warnings - thus we will be able to fix them before actually trying to migrate to 0.12.

Update I created a #24169 that includes both the changelog and the actual patch

nyurik added a commit to nyurik/terraform that referenced this pull request Feb 20, 2020
nyurik added a commit to nyurik/terraform that referenced this pull request Feb 20, 2020
nyurik added a commit to nyurik/terraform that referenced this pull request Feb 20, 2020
@nyurik
Copy link
Contributor Author

nyurik commented Feb 20, 2020

Update -- seems that 0.11 had a different output code. I did make a backport for v0.12 #24169 - hopefully can be merged & published soon. Thanks!

@ghost
Copy link

ghost commented Apr 1, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 1, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Terraform 0.12 shows warnings only when there are changes
2 participants