Open azure-walker opened 2 years ago
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Jingshu923, @zhangyd2015, @Frey-Wang.
Author: | azure-walker |
---|---|
Assignees: | - |
Labels: | `question`, `Data Factory`, `Service Attention`, `customer-reported`, `needs-triage`, `CXP Attention` |
Milestone: | - |
This is related to the general CI/CD process. @leni-msft , could you please help with this ask?
@Frey-Wang It seems you need support specifying branches for all your APIs. I'd suggest asking your architect or ARM API reviewers.
I see that the Service team has already been involved on this.
Hi @azure-walker , could you please provide an example on your request? I'm not sure how can I help to change branch policies.
I am trying to come up with a solution that will allow me to edit a branch of the repository that is not the main line. I need this in order to make changes to pipelines in Azure Data Factory. Currently, the only way to use the azure-mgmt-datafactory is to edit the collaboration branch. I have a lot of pipelines with settings that need to be changed in my test branches. The only way to automate this process is to edit the blobs in the branches. I need to make the change, add and commit the changes but I am not sure how to do this using azure-devops packages. The link to the samples is old and not specific to what I need. I am looking for more documentation or examples of how to use code to edit code and add and commit the changes back to the branch.
Hi @azure-walker, I'm still confused here. Is the question related to swagger, ADF SDK, or ADF product?
Currently the Azure mgmt Datafactory can only make changes to the collaboration branch of Azure Data Factory. However, much of the development is done on other branches. Furthermore, any mass updates that need to be applied to a branch outside of the collaboration branch cannot be done using the azure-mgmt-datafactory package. What is needed in the package is a way to change branches from collaboration to any of the other branches and make changes to the underlying code. This should be applied to any service that is backed by a code repository.