1.1 Common Variables

Common Configuration

Name	Description	Required	Default	Notes
admin_user	Admin User (for AAP and/or Hub)	false	'admin'
admin_password	Admin Password (for AAP and/or Hub)	true
aap_verison	AAP Version to Use	true	'2.3'	Can also be '2.4' currently
redhat_username	Red Hat Subscriber Username	true
redhat_password	Red Hat Subscriber Password	true
redhat_registry_username_vault	Red Hat Subscriber Username	true
redhat_registry_password_vault	Red Hat Subscriber Password	true
manifest_content	Base64 encoded Manifest to Entitle	true		Can be loaded directly from a file using a construct like this: `"{{ lookup('file', '~/Downloads/manifest.zip')
automation_hub_url_vault	Subscriber-specific URL for Content	true		This refers to the automation hub section on https://console.redhat.com. It is the endpoint that is used to download Validated Content in addition to any public Galaxy content needed
automation_hub_token_vault	Subscriber-specific token for Content	true
automation_hub	Flag to build an enable Automation Hub	false	false
controller_configs_dir	Directory to pass to controller_configuration	true		This directory is the key one to load all other AAP Controller configuration. The framework is not opinionated about how the directory gets there - you may wish to generate it yourself or check it out from a git repo
controller_launch_jobs	List of jobs to run after controller_configuration has run	false		Use this to start a job (or jobs) that do not have aggressive schedules, and that are ready to run as soon as the controller is configured. The fewer jobs listed here the better.

Initialization Environment Configuration

Name	Description	Required	Default	Notes
init_env_collection_install	Whether to install collections required by the framework	false	true
init_env_collection_install_force	Whether to use the force argument when installing collections	false	false	Forces the installation of declared dependencies if true
special_collection_installs	"Bundled" collection installations (references files in repodir)	false	[]	A mechanism to allow the installation of collections bundled into the pattern, if the ones published in galaxy and/or Automation Hub are not sufficient
offline_token	Red Hat Offline Token	false		Used to build the imagebuilder image

Automation Hub Specific Configuration

Name	Description	Required	Default	Notes
aap_admin_username	Admin User (for AAP)	false	'{{ admin_user }}'
aap_admin_password	Admin Password (for AAP)	true	'{{ admin_password }} '
private_hub_username	Admin User (for Automation Hub)	true	'{{ admin_user }}'
private_hub_password	Admin Password (for Automation Hub)	true	'{{ admin_password }} '
custom_execution_environments	Array of Execution Environments to build on Hub	true	[]	The execution environments will be built on the hub node, and then pushed into the hub registry from there.

AWS-Specific Configuration

Name	Description	Required	Default	Notes
aws_account_nbr_vault	AWS Account Number	false
aws_access_key_vault	AWS Access Key String	false
aws_secret_key_vault	AWS Secret Key String	false
ec2_region	EC2 region to use for builds	false
ec2_name_prefix	Text to add for EC2	false		This is a name to disambiguate your pattern from anything else that might be running in your AWS account. A VPC, subnet, and security group is built from this, and the prefix is added to the pattern_dns_zone by default. Additionally, the SSH private key is stored locally in ~/{{ ec2_name_prefix }}.
pattern_dns_zone	Zone to use for route53 updates	false
build_idm	Flag to build an idm VM on AWS	false	false	This is a flag to indicate whether to build a VM called idm on AWS, for later installation of the idm software. Note that the framework just instantiates the VM, it does not install the IDM software.
build_sat	Flag to build a Satellite VM on AWS	false	false	This is a flag to indicate whether to install a Satellite VM on AWS, for later installation of the Satellite software. The framework does not include the Ansible code to install Satellite itself.

ImageBuilder-Specific Configuration

Note: If you are providing an AMI via the imagebuilder_ami variable as opposed to building one from console.redhat.com for the pattern, the pattern still assumes that the RHEL instance will be entitled and will be running a suitable version of RHEL.

Name	Description	Required	Default	Notes
org_number_vault	Red Hat Subscriber Organization Number	true		This is the organization number associated with the RHEL instances you need to entitle
activation_key_vault	Activation Key Name to embed in image	true		This is an activation key for the Red Hat CDN. It is expected to be able to enable both the base RHEL repos and the AAP repos.
skip_imagebuilder_build	Flag to skip imagebuilder build (also set imagebuilder_ami if true)	false	false
imagebuilder_ami	AMI to use for VM creation in AWS	false		It is very possible to re-use another imagebuilder build from a previous installation of the pattern framework, and saves ~15 minutes on a new pattern install to re-use such an image.