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_synapse_workspace: Adding sql_identity_control_enabled #10033

Merged
merged 7 commits into from
Jan 13, 2021

Conversation

allantargino
Copy link
Contributor

@allantargino allantargino commented Jan 3, 2021

sql_identity_control_enabled allows Synapse pipelines (running as workspace's system assigned identity) to access SQL pools.

References:

@allantargino
Copy link
Contributor Author

The acceptance test is failing due to a HTTP 201 (created) not being accepted as success by the SDK.
The fix was recently release on v49.1.0.
So this PR is depended on #9683.

@allantargino
Copy link
Contributor Author

BTW not sure if workspace_identity_control_for_sql_enabled is a good property name 🤔

@katbyte
Copy link
Collaborator

katbyte commented Jan 3, 2021

We can probably drop workspace and go with sql_identity_contorl_enabled?

@allantargino
Copy link
Contributor Author

Agreed 👍

@allantargino allantargino changed the title azurerm_synapse_workspace: Adding workspace_identity_control_for_sql_enabled azurerm_synapse_workspace: Adding sql_identity_control_enabled Jan 4, 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 @allantargino, looks like we have some test failures now to fix up, thenn this should be good to merge:

------- Stdout: -------
=== RUN   TestAccSynapseWorkspace_complete
=== PAUSE TestAccSynapseWorkspace_complete
=== CONT  TestAccSynapseWorkspace_complete
    testing.go:684: Step 0 error: errors during apply:
        
        Error: Granting workspace identity control for SQL pool: synapse.WorkspaceManagedIdentitySQLControlSettingsClient#CreateOrUpdate: Failure responding to request: StatusCode=201 -- Original Error: autorest/azure: Service returned an error. Status=201 Code="Unknown" Message="Unknown service error" Details=[{"id":"subscriptions/*******/resourceGroups/acctest-Synapse-210105203011780445/providers/Microsoft.Synapse/workspaces/acctestsw210105203011780445/managedIdentitySqlControlSettings/default","name":"default","properties":{"grantSqlControlToManagedIdentity":{"actualState":"Enabling","desiredState":"Enabled"}},"type":"Microsoft.Synapse/workspaces/managedIdentitySqlControlSettings"}]
        
          on /opt/teamcity-agent/temp/buildTmp/tf-test832164172/main.tf line 27:
          (source code not available)
        
        
--- FAIL: TestAccSynapseWorkspace_complete (972.51s)

@allantargino
Copy link
Contributor Author

It was failing due a problem in azure sdk v48.x, after merging master it worked well. Thanks @katbyte !

@allantargino allantargino marked this pull request as ready for review January 6, 2021 23:37
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 @allantargino - this LGTM 👍

@katbyte katbyte merged commit d6f339f into hashicorp:master Jan 13, 2021
katbyte added a commit that referenced this pull request Jan 13, 2021
@allantargino allantargino deleted the synapse-sql-allow-pipelines branch January 13, 2021 12:26
@ghost
Copy link

ghost commented Jan 14, 2021

This has been released in version 2.43.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example:

provider "azurerm" {
    version = "~> 2.43.0"
}
# ... other configuration ...

@ghost
Copy link

ghost commented Feb 12, 2021

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!

@ghost ghost locked as resolved and limited conversation to collaborators Feb 12, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants