[CICD] Pull required version-n-go CICD scripts from template-specific repo versus Cobalt

[awkwardindustries]

Description

• As an application developer using the version-n-go process to setup my application repository, I'd like to pull the dependent scripts from my template repository versus the Cobalt repository in order to allow for template-specific modification and adjustment as necessary.*

Acceptance Criteria

Reference: [Done-Done Checklist] (https://github.com/Microsoft/code-with-engineering-playbook/blob/master/Engineering/BestPractices/DoneDone.md)

• [ ] Should execute CICD pipeline with devops/providers/azure-devops/templates/infrastructure/scripts/* pulled from the organizational/template-specific repository versus Microsoft/Cobalt.
• [ ] Should pin pull to a specific tagged version of the repository.

Also, here are a few points that need to be addressed:

1. Preference to utilize the application.yml repository resource without having to add additional variables, but not sure if they are accessible in a pre-defined way;
2. Need to handle Git repo credentials in the case that the organizational/template-specific repository is private.

Resources

Driven by comments from PR #280

Tasks

Stories are intended to be completed in a single sprint; if task breakdown creates addition work then team should discuss promoting the Story to an Epic. Reference: [Minimal Valuable Slices] (https://github.com/Microsoft/code-with-engineering-playbook/blob/master/Engineering/BestPractices/MinimalSlices.md)

Reference: [How to Write Better Tasks] (http://agilebutpragmatic.blogspot.com/2012/04/splitting-story-into-tasks-how-to-write.html)

Assignee should break down work into tasks here

[awkwardindustries]

298 is a better solution for the version-n-go process that would not require an additional script download step.