fix(parameter_storage_definition): derive slug output from the created resource#436
Merged
sebastiancorrea81 merged 1 commit intoJul 14, 2026
Merged
Conversation
…d resource The slug output was sourced from the rendered template's local.config.slug instead of the specification resource's own attribute, so it carried no dependency edge on the resource and could expose a value that mismatches what the API actually assigns, causing dependents to run before the specification exists. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
davidf-null
approved these changes
Jul 14, 2026
sebastiancorrea81
deleted the
fix/parameter-storage-definition-slug-output
branch
July 14, 2026 18:50
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.
Summary
output "slug"inparameter_storage_definitionwas sourced fromlocal.config.slug(the rendered template), not from thenullplatform_provider_specificationresource itself.slugattribute is server-computed (only known after apply), reading it from the template instead broke the implicit dependency edge: Terraform didn't know that anything consuming this output must wait for the specification to actually be created.parameter_storage_configuration.provider_specification_slug = module.parameter_storage_definition.slugrace against the specification creation, and the value returned could mismatch whatever slug the API actually assigned.Fix
Point the output at
nullplatform_provider_specification.parameter_storage_specification.sluginstead, so the value is both correct and forces the right ordering.Test plan
terraform planon a root module consuming bothparameter_storage_definitionandparameter_storage_configurationshowsprovider_specification_slugas(known after apply)instead of a statically-resolved value, confirming the dependency edge exists.terraform applycreates the specification before the config resource (no more race).🤖 Generated with Claude Code