Correct uptime check default values #70
Merged
Conversation
This file contains 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
There are some edge cases when using default values, centring mainly around 0 and how Go interprets this value as equivalent to the zero-value of an integer. Even when set explicitly to 0 Terraform is not able to distinguish between the zero-value of an integer and 0. Additionally a few minimum and maximum values have been set on the relevant schema attributes.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
There are some edge cases when using default values, centring mainly
around 0 and how Go interprets this value as equivalent to the
zero-value of an integer. Even when set explicitly to 0 Terraform is not
able to distinguish between the zero-value of an integer and 0.
Additionally a few minimum and maximum values have been set on the
relevant schema attributes.