provider/aws: Rename 'timeout' to 'build_timeout' for Codebuild #12503
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.
Step one of a fix to attribute collision between
aws_codebuild
andhelper/schema/resource_timeout
.Both Codebuild and the new Timeouts feature have a root level name of
timeout
, which was causing a panic in Terraform. Guarding against the panic has been fixed in aa3677c.This PR renames
aws_codebuild
's argument oftimeout
tobuild_timeout
, to further distinguish and just give a better name to what the argument does.This is a BACKWARDS INCOMPATIBILITY however the
aws_codebuild
resource was just released, and I felt the impact minimal. The only thing required is to update the configuration name fromtimeout
tobuild_timeout
in the configuration, that while is breaking, is much clearer in the intent.This is intended for the
v0.9
release branch only