CI/CD Azure Synapse Analytics with GitHub Actions

Darrick B 0

Trying to create a CI/CD process using GitHub Actions without having to click the publish button in a synapse workspace, as well as, merge between different environments. Is it possible to do via GitHub actions without having to use Azure DevOps?

Darrick B 0 Reputation points

2024-08-26T19:58:32.4033333+00:00

Hi @Sina Salam

Not sure if you saw my comment to your initial response but I have created secrets for my client id, tenant id, subscription id, and access token but have yet to create a secret for my various environments - so will give that a try. What keyword specifically keeps me from having to click the publish button in any synapse workspace environment? I am trying to create this CI/CD process or deployment for an azure synapse analytics workspace (web-native) and not a web app. I'm using the following link as a reference, but I'm getting errors when following advised steps:https://learn.microsoft.com/en-us/azure/synapse-analytics/cicd/continuous-integration-delivery?source=recommendations

Specifically, when adding your workflow in github actions it states remaining workflow should appear as such:

Next step is to rename your workflow and add a synapse workspace deployment action, but when trying to add script for workspace deployment I'm receiving an error of duplicated key when adding the name key for workspace deployment. What's also confusing is the keys used from initial step seem to disappear from the overall script on step 4 below. The link also does not advise on how to deploy to different environments. Am I to create 3 different work flows for each environment?
NIKHILA NETHIKUNTA 2,395 Reputation points Microsoft Vendor

2024-08-28T15:27:32.43+00:00

@Darrick B
If you have a support plan could you please file a support ticket for deeper investigation and do share the SR# with us? In case if you don't have a support plan please let us know here.
NIKHILA NETHIKUNTA 2,395 Reputation points Microsoft Vendor

2024-08-30T06:13:26.0533333+00:00

@Darrick B
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Darrick B 0 Reputation points

2024-08-30T13:57:00.03+00:00

@NIKHILA NETHIKUNTA -

Support request ID 2408300040004676

1 answer

Sina Salam 10,491 Reputation points

2024-08-24T06:09:34.7566667+00:00
Hello Darrick B,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

I understand that you are creating a CI/CD process using GitHub Actions and you would want to streamline your work environment using only GitHub actions without having to use Azure DevOps environment.

Yes! You can configure Continuous Integration (CI) and Continuous Deployment (CD) workflows using GitHub Actions without relying on Azure DevOps. Infact, you can:

Create workflows in your GitHub repository using YAML files. These workflows can automatically build, test, and deploy your code based on triggers (such as pushes, pull requests, or scheduled events).

Use GitHub Actions to automate the deployment process.

Define environment-specific variables (secrets) in GitHub repository settings or use GitHub secrets.

Store sensitive information (such as connection strings, API keys) securely using GitHub secrets.

Check the links below for more detailed instructions:

https://datascientest.com/en/azure-devops-vs-github-actions-which-is-the-best-ci-cd-tool.

https://learn.microsoft.com/en-us/azure/app-service/deploy-github-actions.

Accept Answer

I hope this is helpful! Do not hesitate to let me know if you have any other questions.

** Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful ** so that others in the community facing similar issues can easily find the solution.

Best Regards,

Sina Salam
Please sign in to rate this answer.
Darrick B 0 Reputation points

2024-08-25T13:52:27.1633333+00:00

I have created secrets for my client id, tenant id, subscription id, and access token but have yet to create a secret for my various environments - so will give that a try. What keyword specifically keeps me from having to avoid to click the publish button in any synapse workspace environment? I am trying to create this CI/CD process or deployment for an azure synapse analytics workspace (web-native) and not a web app.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

CI/CD Azure Synapse Analytics with GitHub Actions

1 answer

Your answer