I am mapping out a deployment for our environment and I wanted to run it by the group and discuss:
Lifecycle path of Library->Dev/qa->prod. Under each life cycle environment I will create content views for each instance type of hosts and tie the host collections and activation keys to that.
Instance type 1…x would each have their own CV. Each activation key would be tied to a CV for each instance type with each LCE.
- Instance type 1 - staging -> key1
- instance type 1 - Prod - > key2
For content views now, I am thinking of allowing access to all repos and creating an exclude all, then creating yum filters including all the packages I want for each instance in each CV.
Is this best practice or is there a cleaner way?