@Ankita Dhaktod Welcome to Microsoft Q&A forum and thanks for reaching out here.
When dealing with ADF with Source control Enabled, there are few things to be considered. The status of the triggers that you are seeing in Live mode is what's been published to
adf_publish
brach frommain branch
.
In case if you have created a pull request frommain branch
to yourlocal branch
and made changes to your triggers (either from stop to start or from start to stop) and published it back tomain branch
from yourlocal branch
then those changes will not be reflected in ADF Live mode unless they are being published toadf_publish
branch frommain branch
.Kindly ensure that whatever the changes published to your
main branch
are being published toadf_publish
branch.As per your statement, my understanding is that your triggers being enabled in Git mode and being published to
main branch
but not theadf_publish
branch which is there is a discrepancy.
Below is additional info that could help get better understanding of the stages of ADF source control changes.
Collaboration branch: Your Azure Repos collaboration branch that is used for publishing. By default, it's main
. Change this setting in case you want to publish resources from another branch.
Local branch: This is nothing but another/replication of the collaboration branch (main branch) with a different name.
Publish branch: The Publish branch is the branch in your repository where publishing related ARM templates are stored and updated. By default, it's adf_publish
.
Additional Reference:
- ADF publish confusion in git mode
- Source control in Azure Data Factory
- If you would like to start or stop triggers using powershell please follow these documents: Start-AzureRmDataFactoryV2Trigger and Stop-AzureRmDataFactoryV2Trigger
Hope this info helps. Please let me know if you have any questions.
Please don’t forget to Accept Answer
and Yes
for "was this answer helpful" wherever the information provided helps you, this can be beneficial to other community members.