![]() ![]() To take that one step further, it would be amazing to be able to approve such 'optional' stages with a /azp run foo GitHub comment. Before you can run your Datastage commands you will have to run the following commands cd cat /.dshome This will change the location to the home directory. It would be extremely useful for us to be able to have a stage (or stages) in our YAML pipeline that will only run when explicitly triggered by a team member. I tried to test this out today and I can't configure a manual check on a resource that I personally created. We plan to make infrstructure admins custodians for approvals, configure them as a check on the resource (agent pool, variable group, service connection, or secure file), and any stage that uses that resource will be paused for an approval. Configure the enableStaging setting in the copy activity to specify whether you want the data to be staged in storage before you load it into a destination data store. Are there any plans to extend on or modify the design constraints in the future?Ĭonfig-as-code poses interesting challenges for where you specify approvals.
0 Comments
Leave a Reply. |