You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
test_spn_crawler_with_available_secrets detects secret id on an existing legacy spn cluster, but could not detect the spn secret stored in secret scope or the storage account
…` inside secret scope is not detected (#942)
## Changes
- Fix tenant_id detection logic In the case where spn endpoint
configuration is also inside a secret scope.
- Refactoring spn crawler logic to make it more readable
### Linked issues
Closes#896
### Tests
<!-- How is this tested? Please see the checklist below and also
describe any other relevant tests -->
- [x] manually tested
- [ ] added unit tests
- [ ] added integration tests
- [ ] verified on staging environment (screenshot attached)
…` inside secret scope is not detected (#942)
## Changes
- Fix tenant_id detection logic In the case where spn endpoint
configuration is also inside a secret scope.
- Refactoring spn crawler logic to make it more readable
### Linked issues
Closes#896
### Tests
<!-- How is this tested? Please see the checklist below and also
describe any other relevant tests -->
- [x] manually tested
- [ ] added unit tests
- [ ] added integration tests
- [ ] verified on staging environment (screenshot attached)
Is there an existing issue for this?
Current Behavior
test_spn_crawler_with_available_secrets
detects secret id on an existing legacy spn cluster, but could not detect the spn secret stored in secret scope or the storage accountRelated issues:
Expected Behavior
Both secret scope & storage account should be populated
Steps To Reproduce
No response
Cloud
Azure
Operating System
macOS
Version
latest via Databricks CLI
Relevant log output
No response
The text was updated successfully, but these errors were encountered: