Skip to content

configs: More interpolation-only expr deprecations#26105

Merged
alisdair merged 1 commit intomasterfrom
alisdair/more-interpolation-only-expression-deprecations
Sep 16, 2020
Merged

configs: More interpolation-only expr deprecations#26105
alisdair merged 1 commit intomasterfrom
alisdair/more-interpolation-only-expression-deprecations

Conversation

@alisdair
Copy link
Copy Markdown
Contributor

@alisdair alisdair commented Sep 2, 2020

Extend the deprecation for interpolation-only expressions to include module calls, data sources, outputs, and locals.

This PR is targeting the 0.14.0 release. If merged, I'm not sure if it should be cherry-picked to 0.13.x or not. Thoughts?

Fixes #25430, fixes #25828, supersedes #25465.

Extend the deprecation for interpolation-only expressions to include
module calls, data sources, outputs, and locals.
@alisdair alisdair added this to the v0.14.0 milestone Sep 2, 2020
@alisdair alisdair requested a review from a team September 2, 2020 20:42
@alisdair alisdair self-assigned this Sep 2, 2020
@codecov
Copy link
Copy Markdown

codecov bot commented Sep 2, 2020

Codecov Report

Merging #26105 into master will increase coverage by 0.00%.
The diff coverage is 100.00%.

Impacted Files Coverage Δ
configs/module_call.go 69.23% <100.00%> (+1.66%) ⬆️
configs/named_values.go 67.96% <100.00%> (+0.76%) ⬆️
configs/resource.go 82.08% <100.00%> (+0.27%) ⬆️
terraform/node_resource_plan.go 91.80% <0.00%> (-1.64%) ⬇️

Copy link
Copy Markdown
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.

This looks good to me! It'll be nice to expand the warning coverage to be more consistent.

Regarding when to release, I think it would make sense to release this in a 0.13.x, but I'd prefer to wait until a little later in the release period when we feel like we've taken care of the most significant upgrade-related blockers, so that folks upgrading won't feel pressured to deal with these deprecations at the same time as the upgrade steps. On our current trajectory that seems like maybe one more 0.13.x release to address some of the remaining upgrade concerns, and then we could issue one containing these deprecations. (Of course, we'll see how things really look once we've made the next 0.13.x release.)

@alisdair alisdair modified the milestones: v0.14.0, v0.13.x Sep 3, 2020
@alisdair alisdair merged commit 803c95e into master Sep 16, 2020
@alisdair alisdair deleted the alisdair/more-interpolation-only-expression-deprecations branch September 16, 2020 20:06
@ghost
Copy link
Copy Markdown

ghost commented Oct 17, 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 as resolved and limited conversation to collaborators Oct 17, 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 syntax warnings do not check data source or output blocks Terraform Validate does not throw warnings for deprecated syntax inside modules

2 participants