search

MicrosoftDocs / azure-docs

Open source documentation of Microsoft Azure
https://docs.microsoft.com/azure
Creative Commons Attribution 4.0 International
10.22k stars 21.37k forks source link

Missing information for programmatic setup of Synapse - Git integration #81205

Closed jwefers closed 4 months ago

jwefers commented 3 years ago

Greetings,

i am trying to set up the integration between Synapse and a DevOps Git repo. However, i dont want/can't do that via GUI workflow. Infrastructure as Code (Terraform here) is the way. So terraform indeed allows me to specify a devops repo as target:

resource "azurerm_synapse_workspace" "example" {
  ...
  azure_devops_repo {
    account_name    = var.azure_devops_repo.account_name
    branch_name     = var.azure_devops_repo.branch_name
    project_name    = var.azure_devops_repo.project_name
    repository_name = var.azure_devops_repo.repository_name
    root_folder     = var.azure_devops_repo.root_folder
  }
...
}

But there is absolutely no information available on what and which permissions i have to set up on the DevOps side to make that integration work. Also, no info on what is happending under the hood when i use the UI flow. Would this create a PAT for the user thats doing the flow?

Please add information on how to create this integration programmatically, and specifically, so that it works without actual user accounts involved, but Service Principals.

Thanks and Best

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

jwefers commented 3 years ago

After observing what the portal does when setting up the "integration" i understand that there is no backend work involved. Its just that the Synape Studio Frontend app gets a token for my user for devops, sets the repo details as a sort of bookmark and the rest is just git commits via REST using my own creds.

Maybe this can be reflected in the docs

MartinJaffer-MSFT commented 3 years ago

Thank you for your feedback. This has been assigned to the content owner and will be updated as appropriate.

bandersmsft commented 4 months ago

Thanks for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. We are closing this issue for now, but if you feel that it's still a concern, please respond and let us know. If you determine another possible update to our documentation, please don't hesitate to reach out again. #please-close