Flags to specify template source components

[jeffcpullen]

ISSUE TYPE

• Feature Idea

SUMMARY

It appears that this tool bundles the "best practice" collection template. There are at least two major use cases which could benefit from the ability to modify that template.

1. Teams and organizations that have code reuse within their collections for either metadata and/or testing.
2. Teams that deliberately deviate from "best practices" with the knowledge that it can't/wont be shared to the public.

Providing a method to have ansible-creator deploy this customized template instead of the one included would be especially helpful in both use cases.

I could imagine this tool being used to generate an initial base template that can be modified and then referenced back in as the source once the changes are saved. Having the ability to reference a git repo would make it easy to share within an organization or to the public. This would have the added value of reducing the friction of contributing to collection template best practices by separating the content from the code.

Expanding on this idea, if there were more options to the template source that allowed the user to pick and choose which areas to override would make it simpler for teams, vendors and other related projects to provide templates relevant to areas of interest. For example a team could reference content for Azure DevOps or Gitlab CI rather than GitHub Workflows. This is also very relevant for the testing as the molecule test infrastructure requires different templates depending on the hosting provider used by the team.

[cidrblock]

This is a great idea!