zone: Remove DiffSuppressFunc causing jump_start issues
#830
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
Updates the `cloudflare_zone` schema to remove `DiffSuppressFunc` for `jump_start`. From the test case in cloudflare#826, this attribute is causing the value to always be set to "false" which is preventing the end users value from being passed through to the API call. The history suggests this has always been the case since the resource was introduced so I'm not sure if it was intentional, however this addresses the bug in question. Fixes cloudflare#826
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.
Updates the
cloudflare_zoneschema to removeDiffSuppressFuncforjump_start. From the test case in #826, this attribute is causing thevalue to always be set to "false" which is preventing the end users
value from being passed through to the API call.
The history suggests this has always been the case since the resource
was introduced so I'm not sure if it was intentional, however this
addresses the bug in question.
Fixes #826