[Feat]: Improve auto-create-repository behaviour within Deployment Map Definition

[alexevansigg]

Describe the feature

In the ADF config we can define a 'auto-create-repositories' flag. This is a global setting which applies to all pipelines. But it's inflexible.

Use Case

In our environment we have a lot of deployment maps, and we like to redeploy the entire solution to multiple organizations.
There are some cases where multiple pipelines run using the same source repository, for example when you reach the 500action limit in a pipeline it might be carved into multiple pipelines point to the same source.

Proposed Solution

The following changes:

1. Add a property in pipeline definition source section called 'create-repository-override': boolean.
2. Like we can set a custom source repository name, extend to allow setting a custom repository description, As the Pipeline description might be different from the repository description.
3. Update the logic in the Create-Pipeline CodeBuild job so that it can create 'Custom named' Repositories, it uses custom repository descriptions specified and that it honors the Pipeline definition override when specified.

Acknowledgements

• I may be able to implement this feature request

[sbkok]

Thank you for opening this issue.

Regarding the proposed solution:

1. If you create a pipeline and set a repository name that is different from the pipeline name, it will not create the repository for you. Instead, it assumes this pipeline hooks into an existing repository, like the mono-repo approach you described. Would you still see a need for a create-repository-override?
2. Good idea, that could be a valuable property to add.
3. What do you mean with custom named repositories? Are you proposing defining a pipeline with a name that is different from the repository, yet still instruct ADF to create the repository for you?