chore: unify nullplatform provider version (~> 0.0.86) and module hygiene#405
Merged
Merged
Conversation
Standardize the nullplatform provider version across the 26 modules that
declare it. Most used the unbounded ">= 0.0.86" (no ceiling on a 0.0.x
provider, so `init -upgrade` could pull any future breaking release),
plus two outliers: scope_configuration ("~> 0.0.67") and asset/ecr
("~> 0.0.88").
Switch all to "~> 0.0.86" (allows 0.0.x patches, blocks 0.1.0+) and
regenerate every .terraform.lock.hcl so the locked nullplatform version
is uniform at 0.0.95, with hashes for linux_amd64, darwin_amd64 and
darwin_arm64. Other providers' lock entries are left untouched.
…nsistency Match the providers.tf filename used by the other 25 nullplatform modules.
- users: validate email format and require at least one role_slug - metrics: require prometheus_url to be http(s) when set - scope_configuration: require non-empty provider_specification_slug - scope_definition_agent_association: validate github_repo_url is an HTTP(S) URL and add the missing description on the nrn variable
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
Normalizes the
nullplatformprovider usage across all 26 modules undernullplatform/and adds some module hygiene. Three logical commits:1. Unify the provider version constraint (
chore(deps))~> 0.0.86.>= 0.0.86(no ceiling on a0.0.xprovider, soinit -upgradecould pull any future breaking release), plus two outliers —scope_configuration(~> 0.0.67) andasset/ecr(~> 0.0.88)..terraform.lock.hclso the locked provider version is uniform at0.0.95(the current latest, within~> 0.0.86), with hashes forlinux_amd64,darwin_amd64anddarwin_arm64. Other providers' lock entries are untouched.2. Standardize file naming (
chore)scope_configuration/provider.tf→providers.tfto match the other 25 modules.3. Input validation + missing descriptions (
feat)users: validate email format and require at least onerole_slug.metrics:prometheus_urlmust behttp(s)when set.scope_configuration:provider_specification_slugmust not be empty.scope_definition_agent_association: validategithub_repo_urlis an HTTP(S) URL and add the missingdescriptionon thenrnvariable.Why
>= 0.0.86with no ceiling is risky on a0.0.xprovider (every release can be breaking).~> 0.0.86keeps patch updates within0.0.xbut blocks0.1.0+. Unifying the constraint and the lockfiles makes provider resolution reproducible and consistent across modules. The validations catch common misconfigurations atplantime instead of failing against the API.Verification
tofu validatepasses on the touched modules.0.0.86and0.0.95: only additive-optional fields and relaxations (e.g.provider_config.dimensionsRequired→Optional), no removed attributes, no newRequired, no newForceNew— i.e. the version bump is backward-compatible.