Add recommendation around collections bakes into an EE vs. pulled via collections/requirements.yml

redhat-cop / automation-good-practices

Recommended practices for all elements of automation using Ansible, starting with collections and roles, continuing with playbooks, inventories and plug-ins... These good practices are planned to be used by all Red Hat teams interested but can of course be used by others.

268 stars 66 forks source link

Add recommendation around collections bakes into an EE vs. pulled via collections/requirements.yml #73

Open ericzolf opened 2 years ago

ericzolf commented 2 years ago

We might want to create a new AAP section for this, but let's first try to get some kind of consensus within the community, so let's start the discussion.

djdanielsson commented 2 years ago

I wonder if we should cover a few different development styles and how if your company follows one of those styles then which way we would suggest you deal with this.

branic commented 2 years ago

I agree with @djdanielsson, I don't think there is a "one size fits all" solution. Things like how often a collection is updated, how often it is used, and potentially even how big it is can affect the decision whether to bake it into an EE or pull it in via a requirements.yml during runtime. The development style and maturity of an organization also makes a difference (e.g. is building EEs a manual or automated process).