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

azurerm_databricks_workspace - Upgrade Databricks API to the 2021-04-01-preview version #12543

Merged
merged 21 commits into from
Jul 30, 2021

Conversation

WodansSon
Copy link
Collaborator

@WodansSon WodansSon commented Jul 10, 2021

NOTE: This PR cannot be merged until the service team removes the subscription level feature flag from Azure excluding all subscriptions who have not registered the feature flag within their subscription from calling this API version, else it would break all customers currently using the Terraform Databricks resource.

ADDITIONAL: Service team has indicated that this version of the API will be callable by all subscriptions on the 26th of July. So I have moved this into the v2.70.0 Release.

ADDITIONAL ADDITIONAL: Removing the feature flag for the API is taking longer than expected to roll out and is now estimated to be complete by Friday 7/30/2021. So I have moved this into the v2.71.0 Release.

  • Dependencies: Upgrade Databricks API to the 2021-04-01-preview version
  • New Data Source: azurerm_databricks_workspace_private_endpoint_connection

Added fields:

  • public_network_access_enabled
  • network_security_group_rules_required
  • load_balancer_backend_address_pool_id
  • nat_gateway_name
  • public_ip_name
  • storage_account_name
  • storage_account_sku_name
  • vnet_address_prefix
  • public_subnet_network_security_group_association_id
  • private_subnet_network_security_group_association_id

Data Source fields:

  • workspace_id
  • private_endpoint_id
  • connections block

    connections block fields:

    • workspace_private_endpoint_id
    • name
    • status
    • description
    • action_required

Examples:

  • Added an example configuration file on how to correctly configure Databricks Workspace with Private Link Endpoint.

fixes #11158
fixes #7799

@WodansSon WodansSon modified the milestones: v2.68.0, v2.69.0 Jul 15, 2021
@WodansSon WodansSon changed the title [WIP]azurerm_databricks_workspace - Upgrade Databricks API to the 2021-04-01-preview version azurerm_databricks_workspace - Upgrade Databricks API to the 2021-04-01-preview version Jul 17, 2021
@WodansSon WodansSon modified the milestones: v2.69.0, v2.70.0 Jul 20, 2021
Copy link
Collaborator

@katbyte katbyte left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @WodansSon - just a couple comments left inline

Comment on lines 114 to 121
"load_balancer_backend_pool_name": {
Type: pluginsdk.TypeString,
ForceNew: true,
Optional: true,
AtLeastOneOf: workspaceCustomParametersString(),
},

"load_balancer_id": {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you get the name from the id?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, I cannot get the backend name from the load balancer but I can get the load balancer ID from the backend pool id. 🤔

Copy link
Collaborator Author

@WodansSon WodansSon Jul 22, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed... I have removed the two custom parameters(e.g. load_balancer_backend_pool_name and load_balancer_id) and replaced it with a single top level parameter load_balancer_backend_address_pool_id. Since this field is not real, I had to do some magic behind the curtains to get it to work and inject the values into the custom parameters struct of the ARM call. That said, it appears to be correct since my local test cases are working, azure portal and the state file appears to be correct as well.

Default: true,
},

"require_network_security_group_rules": {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we be consistant with the tense?

Suggested change
"require_network_security_group_rules": {
"network_security_group_rules_required": {

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed.

AtLeastOneOf: workspaceCustomParametersString(),
},

"storage_account_sku_name": {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we get this from the storage account or is it auto created from the name above:

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, this is auto created by the Databricks RP, it has a default value of standard_GRS I think. This is offered as an override so you can control sku of the auto generated storage account.

@WodansSon WodansSon modified the milestones: v2.70.0, v2.71.0 Jul 29, 2021
@WodansSon
Copy link
Collaborator Author

image

Copy link
Collaborator

@katbyte katbyte left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @WodansSon - LGTM 🍰

@WodansSon WodansSon merged commit 252dde4 into master Jul 30, 2021
@WodansSon WodansSon deleted the e-databricks-upgrade-private branch July 30, 2021 23:02
WodansSon added a commit that referenced this pull request Jul 30, 2021
@github-actions
Copy link

github-actions bot commented Aug 6, 2021

This functionality has been released in v2.71.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

@github-actions
Copy link

github-actions bot commented Sep 6, 2021

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 6, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.