Skip to content

Use the new default value feature in api.yaml in terraform#201

Merged
rosbo merged 2 commits into
masterfrom
default_value
May 18, 2018
Merged

Use the new default value feature in api.yaml in terraform#201
rosbo merged 2 commits into
masterfrom
default_value

Conversation

@rosbo

@rosbo rosbo commented May 17, 2018

Copy link
Copy Markdown
Contributor

Terraform had its own concept of default value. @rambleraptor added this feature to api.yaml yesterday #148. This PR updates Terraform to use the api.yaml default_value feature. As always, you can override it in a provider.

For now, I blindly updated our terraform.yaml file to simply use the override feature. We may, in a separate PR, move some of these values up to api.yaml


[all]

[terraform]

[puppet]

[puppet-dns]

[puppet-sql]

[puppet-compute]

[chef]

@rosbo rosbo requested a review from rambleraptor May 17, 2018 23:57
@rosbo rosbo requested a review from danawillow May 18, 2018 00:00
check_optional_property :validation, Provider::Terraform::Validation
check_optional_property :set_hash_func, String

check_optional_property :update_statement, String

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I also fixed a bug where these lines where in the wrong validate method

checkIntervalSec: !ruby/object:Provider::Terraform::PropertyOverride
default: !ruby/object:Provider::Terraform::Default
value: 5
default_value: 5

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is also set in api.yaml. Any idea whether that was intentional?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, you put that stuff in the PR description, cool. We'll talk about it another time :)

@modular-magician

Copy link
Copy Markdown
Collaborator

I am a robot that works on MagicModules PRs!
I checked the downstream repositories (see README.md for which ones I can write to), and none of them seem to have any changes.

Once this PR is approved, you can feel free to merge it without taking any further steps.

@rosbo rosbo merged commit c09729b into master May 18, 2018
@rosbo rosbo deleted the default_value branch May 18, 2018 00:19
chrisst pushed a commit to chrisst/magic-modules that referenced this pull request Oct 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants