Update cloudposse/utils provider to v2.0.0#110
Merged
Conversation
Update all modules and examples to require utils provider v2.0.0+.
The v2 release fixes a critical plugin crash ("Plugin did not respond")
caused by the embedded Atmos version not understanding newer atmos.yaml
features (stores, hooks, templates.settings.gomplate).
Notable: removes the `< 2.0.0` upper bound from modules/remote-state
that was explicitly blocking v2.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
Important Cloud Posse Engineering Team Review RequiredThis pull request modifies files that require Cloud Posse's review. Please be patient, and a core maintainer will review your changes. To expedite this process, reach out to us on Slack in the |
Member
Author
|
/terratest |
Pin to >= 2.0.0, < 3.0.0 consistently across all modules and examples to guard against future breaking changes in the provider. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Member
Author
|
/terratest |
Member
Author
|
@coderabbitai full review |
milldr
approved these changes
Feb 20, 2026
|
These changes were released in v2.0.0. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
what
cloudposse/utilsprovider version constraint to>= 2.0.0, < 3.0.0across all 13versions.tffiles (root module, 6 child modules, 6 examples)< 2.0.0upper bound frommodules/remote-statethat was blocking the v2 upgrade< 3.0.0upper bound consistently across all modules (previously onlymodules/remote-statehad an upper bound)why
cloudposse/utilsprovider v1.x embeds Atmos v1.189.0, which panics when it encounters neweratmos.yamlfeatures (stores,hooks,templates.settings.gomplate,!terraform.stateYAML tags). This causes a critical "Plugin did not respond" crash indata "utils_component_config", blocking all components that use theremote-statemodule (56+ components in a typical infrastructure repo)atmos.yamlfeatures without crashing< 3.0.0upper bound is applied consistently to all modules and examples to guard against future breaking changes in the provider, following the same pattern previously used only inmodules/remote-statereferences
cloudposse/utilsprovider v2.0.0 release