[Fix] Tolerate databricks_permissions
resources for SQL warehouses with /warehouses/...
IDs
#4158
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
#4143 reported a regression to the
databricks_permissions
resource caused by #3956. Normally, the ID for this resource when configured for a SQL warehouse is/sql/warehouses/<ID>
. However, it seems like at some point in the past, some users may have had an ID of/warehouses/<ID>
. It's possible that importing this resource worked like this: when calling the permissions REST API, whether using object typesql/warehouses
orwarehouses
, the API returns permissions for the same resources:This PR modifies the SQL warehouse configuration for
databricks_permissions
to be chosen for instances with an ID of the form/warehouses/...
.Tests
The additional integration test ensures that a resource can be imported with the
/warehouses/<ID>
format.