Is Synapse workspace deployment task use only incremental mode ?

Question

Is Synapse workspace deployment task use only incremental mode ?

Siddharth Joshi 41

Hi,

I want to know that Synapse workspace deployment task use only incremental mode by default with "validate & deploy" option because my requirement is incrementally but I haven't use "validate & deploy" Sofar but I got to know from other reference links that Synapse workspace deployment task use only incremental mode .

Can you please confirm on this ?

BhargavaGunnam-MSFT 10,321 Reputation points Microsoft Employee

2023-03-02T02:34:05.5066667+00:00

Hello Siddharth Joshi,

Welcome to the MS Q&A platform.

Please correct me if my understanding is wrong. You want to know whether the synapse deployment task supports publishing only specific artifacts?

When you choose the ‘Validate and Deploy’ option in the synapse deployment task, you can deploy the artifacts from a non-publish branch.

Ex: You can create a new feature branch with one artifact(one pipeline) and deploy it using the "validate and deploy" option.

Validate and Deploy is a new feature in v2 that can be used to deploy the workspace artifacts from a non-publish branch directly. If the Validate operation succeeds, the extension will export the ARM templates from the specified root folder, which will serve as the input for the CD process.

Please see the below tech community document explaining in detail about this feature.

https://techcommunity.microsoft.com/t5/azure-synapse-analytics-blog/automating-the-publishing-of-workspace-artifacts-in-synapse-cicd/ba-p/3603042

I hope this helps. Please let me know if you have any further questions.
Siddharth Joshi 41 Reputation points

2023-03-02T05:12:12.8533333+00:00

Hi @BhargavaGunnam-MSFT , Yes we want to use "Incremental mode" in our deployment but our requirement is to deploy multiple feature branch changes as a merged in our develop branch and these deployment should not add previous changes because all feature branches will be created from develop branch only.

So In this condition I though "validate and deploy" option internally use incremental mode but my guess was wrong.

Please let me know what is workaround of my issue.
Siddharth Joshi 41 Reputation points

2023-03-06T09:27:20.01+00:00

Hello Same apply for Synapse Pipeline artifacts as well ?
BhargavaGunnam-MSFT 10,321 Reputation points Microsoft Employee

2023-03-06T17:44:31.5466667+00:00

Hello Siddharth Joshi,

Correct, this applies to synapse pipeline artifacts as well.
Please let me know if you have any further questions here.

If this answers your question, please consider accepting the answer by hitting the Accept answer and up-vote as it helps the community look for answers to similar questions.

BhargavaGunnam-MSFT 10,321 Reputation points Microsoft Employee

2023-03-02T02:34:05.5066667+00:00

Hello Siddharth Joshi,

Welcome to the MS Q&A platform.

Please correct me if my understanding is wrong. You want to know whether the synapse deployment task supports publishing only specific artifacts?

When you choose the ‘Validate and Deploy’ option in the synapse deployment task, you can deploy the artifacts from a non-publish branch.

Ex: You can create a new feature branch with one artifact(one pipeline) and deploy it using the "validate and deploy" option.

Validate and Deploy is a new feature in v2 that can be used to deploy the workspace artifacts from a non-publish branch directly. If the Validate operation succeeds, the extension will export the ARM templates from the specified root folder, which will serve as the input for the CD process.

Please see the below tech community document explaining in detail about this feature.

https://techcommunity.microsoft.com/t5/azure-synapse-analytics-blog/automating-the-publishing-of-workspace-artifacts-in-synapse-cicd/ba-p/3603042

I hope this helps. Please let me know if you have any further questions.
Siddharth Joshi 41 Reputation points

2023-03-02T05:12:12.8533333+00:00

Hi @BhargavaGunnam-MSFT , Yes we want to use "Incremental mode" in our deployment but our requirement is to deploy multiple feature branch changes as a merged in our develop branch and these deployment should not add previous changes because all feature branches will be created from develop branch only.

So In this condition I though "validate and deploy" option internally use incremental mode but my guess was wrong.

Please let me know what is workaround of my issue.
Siddharth Joshi 41 Reputation points

2023-03-06T09:27:20.01+00:00

Hello Same apply for Synapse Pipeline artifacts as well ?
BhargavaGunnam-MSFT 10,321 Reputation points Microsoft Employee

2023-03-06T17:44:31.5466667+00:00

Hello Siddharth Joshi,

Correct, this applies to synapse pipeline artifacts as well.
Please let me know if you have any further questions here.

If this answers your question, please consider accepting the answer by hitting the Accept answer and up-vote as it helps the community look for answers to similar questions.

Answer 1

Hello Siddharth Joshi,

If my understanding is correct, you wanted to cherry-pick commits or selective publishing of resources from your feature branches to the collaboration branches.

If this is correct, cherry-picking is not allowed. However, on rare occasions when you need selective publishing, consider using a hotfix.

Please see the below document explained about the hotfix process.

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/continuous-integration-delivery-hotfix-environment.md

Video tutorial: https://www.microsoft.com/videoplayer/embed/RE4I7fi

You can use Git collaboration feature to manage your pipelines from feature branches and control the changes that merge into the main branch.

In general, all development and testing work will be done on the feature branches and merged into the main branch when ready for deployment. When we publish the changes to the main branch, it will only affect the changes in the main branch and will not affect any changes in other feature branches.

You can create a pull request in the Git repository to merge from a feature branch to the main branch. This will allow you to review and approve the changes before they are merged into the main branch. You can also configure branch policies to enforce certain rules, such as requiring approval from a specific user or group before a pull request can be merged.

User's image

I hope this helps. Please let me know if you have any further questions.

Is Synapse workspace deployment task use only incremental mode ?

1 answer

Activity