Allow to change custom_tags
in databricks_instance_pool
resource without recreating a pool
#2400
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.
Changes
REST API supports editing of tags for quite a some time, but the field was still marked as
force_new
leading to recreation of the pool & affecting dependent resources.Please note that due API bug it's impossible to remove tags completely after they set, you can only change them.
Tests
make test
run locallydocs/
folderinternal/acceptance