Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Databricks control plane IPs are changing 2024-05-30 #3901

Closed
SvenAelterman opened this issue Apr 9, 2024 · 4 comments · Fixed by #3964
Closed

Databricks control plane IPs are changing 2024-05-30 #3901

SvenAelterman opened this issue Apr 9, 2024 · 4 comments · Fixed by #3964
Assignees
Labels
bug Something isn't working storysize/L 1 week (2.5 days)

Comments

@SvenAelterman
Copy link
Collaborator

Describe the bug

Databricks control plane IPs in the json file need to be updated following today's announcement that they are changing effective May 30, 2024.

List: https://learn.microsoft.com/en-us/azure/databricks/resources/supported-regions#--inbound-to-azure-databricks-control-plane

Azure TRE release version (e.g. v0.14.0 or main): N/A

Deployed Azure TRE components - click the (i) in the UI: N/A

@SvenAelterman SvenAelterman added the bug Something isn't working label Apr 9, 2024
@tim-allen-ck
Copy link
Collaborator

This the databricks-udr.json file will need updating
templates/workspace_services/databricks/terraform/databricks-udr.json

@tim-allen-ck
Copy link
Collaborator

@SvenAelterman could you clarify which ips need changing? Or is it all locations?

@tim-allen-ck tim-allen-ck added this to the Release 0.18.0 milestone May 10, 2024
@SvenAelterman
Copy link
Collaborator Author

@tim-allen-ck I don't know, I haven't compared.

@PoojanumN PoojanumN added the storysize/L 1 week (2.5 days) label May 20, 2024
@tim-allen-ck
Copy link
Collaborator

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working storysize/L 1 week (2.5 days)
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

4 participants