Impossible to access Terraform created external location?!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-22-2025 01:54 AM - edited 04-22-2025 02:14 AM
Hi all,
There seems to be an external location created that nobody within the organization can actually see or manage, because it has been created with a Google service account in Terraform.
Here is the problem:
this returns
this confirms that there IS an external location by this name in my workspace, however, as an admin, I am unable to see it in the external locations, neither is anybody else in my organization. I am unable to recreate the external location.... because it already exists. It seems this was created by mistake with terraform, the terraform configuration has since then changed to no longer include this. Now even if we want to recreate this with terraform, we can't because the google bucket location is already taken.
I hope I'm just missing an obvious super admin button somewhere but it really seems that databricks allows users to create inaccessible external locations.
Thanks in advance for your input!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-22-2025 08:43 AM
Are you a workspace admin or a metastore admin? Only Metastore admins should see all UC objects created.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-22-2025 04:33 PM
I would agree that the metastore admin(s) should be able to see the external location. This issue can happen with terraform scripts if the script doesn't grant additional rights on the external location.