Remove noisy azure_workspace_resource_id field not provided message for non-production Databricks deployments
#409
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
… for non-production Databricks deployments JWT mismatched claims errors are only happening for dev and staging deployments of Databricks, adding the unnecessary noise to production users. `azure_workspace_resource_id` is not required for authentication to succeed.
Codecov ReportAttention:
📢 Thoughts on this report? Let us know!. |
|
This can also happen if the user has multiple tenants setup in their azure cli. Miles deduplicated the warning message in here: |
|
This warning message is intentional and is designed to help out users who haven't specified the azure resource ID for workspace they are logging into when using Azure CLI auth. If you specify the azure resource ID in your configuration, that warning message will disappear. |
tanmay-db
approved these changes
Dec 19, 2023
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.
Changes
JWT mismatched claims errors are only happening for dev and staging deployments of Databricks, adding the unnecessary noise to production users.
azure_workspace_resource_idis not required for authentication to succeed.Tests
make testrun locallymake fmtapplied