[FEATURE] databricks_secret_scope is missing databricks workspace reference

[TjommeVergauwen]

Use-cases

We create multiple databricks workspaces in our Terraform setup. This is driven by configuration files. We also create different key vaults for different user groups that need to be linked to certain specific workspaces. Also this is controlled by configuration files indicating which key vault needs to be accessible in which workspace.

Currently this is not possible as the databricks_secret_scope component does not allow to specify for which workspace it is created. It is always the one linked to the provider. It is not possible to define a varying number of providers.

Attempted Solutions

Defining a varying list of providers is not possible. The only way is to predefine a fix set of providers (which can be configured dynamically) which hopefully is bigger than the number of workspaces that are created.

Creating a separate module with its own provider does not work either as calls to this module can't use for_each or count. Doing so results in the following error:

│ The module at module.setDatabricksSecretScope is a legacy module which contains its own local provider configurations, and so calls to it may not use the count, for_each, or depends_on arguments.
│
│ If you also control the module "./modules/terraform-databricks-set_secret_scope", consider updating this module to instead expect provider configurations to be passed by its caller.

Proposal

By adding a reference to a databricks workspace to the databricks_secret_scope, the setup becomes much clearer and more dynamic; That way we are able to create workspaces dynamically and link the different secrets to the appropriate workspace.

References