Azure / Synapse-workspace-deployment

MIT License
27 stars 34 forks source link

Synapse Deployment Workflow Failing #61

Closed vinaysandela closed 2 years ago

vinaysandela commented 2 years ago

Two different error messages received from executing the workflow. When managedIdentity is set to true, we get the message below. The workflow completes successfully but none of the resources show up in the target Synapse workspace. image When managedIdentity is set to false, this message appears and the workflow has "Failed":

image

Please suggest. Thanks

derekadams32 commented 2 years ago

Here is the yaml file in question that is causing the errors above:

name: Azure Synapse Prod Deployment

on:
  workflow_dispatch:
    inputs:
      logLevel:
        description: 'Log level'     
        required: true
        default: 'warning' 
        type: choice
        options:
        - info
        - warning
        - debug 
  push:
    branches: [ workspace_publish ]

jobs:
  release:
    runs-on: [self-hosted, x64, windows, enterprise, azure]
    steps:
      - uses: actions/checkout@v3
        with: 
          ref: 'workspace_publish'
      - uses: Azure/Synapse-workspace-deployment@V1.6.0
        with:
          TargetWorkspaceName: 'my-synapse-workspace'
          TemplateFile: './ghr-dev-syn/TemplateForWorkspace.json'
          ParametersFile: './ghr-dev-syn/TemplateParametersForWorkspace.json'
          environment: 'Azure Public'
          resourceGroup: 'my-resource-group'
          clientId: ${{ secrets.CLIENTID }}
          subscriptionId: ${{ secrets.SUBCRIPTIONID }}
          tenantId: ${{ secrets.TENANTID }}
          clientSecret: ${{ secrets.CLIENTSECRET }}
          operation: 'deploy'
          managedIdentity: false
lordozb commented 2 years ago

Please raise a support ticket on the Azure portal.

  1. For the error with MSI, was it running on a self-hosted VM on azure?
  2. For the error without MSI, does the workspace has any network restrictions or firewall rules? Are the values in the secrets correct? Is the workspace name and resource group correct?