#####################################################################
# COMPLETE ANSWERS
# This answer file documents every answer which should be manipulated in an answer file.
# This answer file will still generate an ALL IN ONE INSTALL

#--------------------------------------------------------------------
# Global Answers
# These answers are always needed.

# Y or N — Whether to install. Answer files must set this to "Y".
q_install=y

# Y or N — Whether the installer has permission to install additional packages
# from the OS’s repositories. If this is set to N, the installation will fail
# if the installer detects missing dependencies.
q_vendor_packages_install=y

# Y or N — Only used on AIX. Whether to run the updtvpkg command to add info
# about native libraries to the RPM database. The answer should usually be Y,
# unless you have special needs around the RPM database.
# These answers are only used in some cases, such as when upgrading or reinstalling.
#q_run_updtvpkg=y

# Y or N — Whether the installer should backup the existing configuration files
# and then purge them, or leave them in place. If set to N the installer will
# fail. This is only needed if Puppet Enterprise was uninstalled without the -p
# option.
#q_backup_and_purge_old_configuration=y

# Y or N — Only used on Upgrade. Whether upgrading should enable use of the new
auth.conf file or the legacy auth.conf file. If there is a custom auth.conf
file that has been found the user has an option to migrate their old
configuration to the new auth.conf file after the upgrade has completed or
continue to use the legacy auth.conf file.
#q_migrate_auth_conf_after_upgrade=y

# Y or N — Only used on Upgrades from PE 3.8. Whether upgrading should stop if
there is a # custom auth.conf file. If there is a custom auth.conf file an
upgrade could # fail if the auth.conf file is not migrated properly.  This
answer exists to # provide a way to upgrade after confirming that auth.conf has
been migrated.
#q_exit_and_update_auth_conf=y

#--------------------------------------------------------------------
# Components
# These answers are always needed.

# Y or N — Whether to install the puppet master role.
q_puppetmaster_install=y

# Y or N — Whether or not the installation is an all-in-one installation,
# (i.e., are puppetdb and the console also being installed on this node). This
# is also known as a monolithic install.
q_all_in_one_install=y

# Y or N — Whether to install the database support (the console PostgreSQL
# server and PuppetDB) role.
#q_puppetdb_install=y

# Y or N — Whether to install the console role.
#q_puppet_enterpriseconsole_install=y

# Y or N — Whether to install the puppet agent role.
#q_puppetagent_install=y

#--------------------------------------------------------------------
# Puppet Agent Answers
# These answers are always needed.

# String — An identifying string for this agent node. This per-node ID must be
# unique across your entire site. Fully qualified domain names are often used
# as agent certnames.
q_puppetagent_certname=pe-puppet.localdomain

# String — The hostname of the puppet master server. For the agent to trust the
# master’s certificate, this must be one of the valid DNS names you chose when
# installing the puppet master.
#q_puppetagent_server=pe-master.localdomain

# Y or N — Whether to quit the install if the puppet master cannot be reached.
#q_fail_on_unsuccessful_master_lookup=y

# Y or N — This is a silent install option, default is N. When set to "Y", the
# installer will skip master verification which allows the user to deploy agents
# when they know the master won’t be available.
#q_skip_master_verification=n

# Y or N — Controls whether or not the puppet agent should run after being installed.
#q_puppet_agent_first_run=y

#--------------------------------------------------------------------
# Puppet Master Answers
# These answers are generally needed if you are installing the puppet master
# role.

# String — An identifying string for the puppet master. This ID must be unique
# across your entire site. The server’s fully qualified domain name is often
# used as the puppet master’s certname.
q_puppetmaster_certname=pe-puppet.localdomain

# String — Valid DNS names at which the puppet master can be reached. Must be a
# comma-separated list. In a normal installation, defaults to
# <hostname>,<hostname.domain>,puppet,puppet.<domain>.
q_puppetmaster_dnsaltnames=pe-puppet,pe-puppet.localdomain

# String — The hostname of the server running the console role. Only needed if
# you are not installing the console role on the puppet master server.
#q_puppetmaster_enterpriseconsole_hostname=pe-puppet.localdomain

# Integer — The port on which to contact the console server. Only needed if you
# are not installing the console role on the puppet master server.
q_puppetmaster_enterpriseconsole_port=443

# y or n; MUST BE LOWERCASE — Whether to check for updates whenever the pe-httpd
# service restarts. To get the correct update info, the server will pass some
# basic, anonymous info to Puppet Labs’ servers. Specifically, it will transmit:
# the IP address of the client
# the type and version of the client’s OS
# the installed version of PE
# the number of nodes licensed and the number of nodes used
# If you wish to disable update checks (e.g. if your company policy forbids
# transmitting this information), you will need to set this to n. You can also
# disable checking after installation by editing the
# /etc/puppetlabs/installer/answers.install file.
q_pe_check_for_updates=y

# String — The location from which PE agent tarballs will be downloaded before
# installation. Note that agent tarballs are only available for certain
# operating systems. For details, see the PE installation instructions
#q_tarball_server=pe-puppet.localdomain

# Y or N - Used when installing on a machine where a previous installation was
# uninstalled without the purge option (-p).  'N' will allow a chance to backup
# an existing configuration and continue installing Puppet Enterprise.
#q_skip_backup=y

# Y or N — Whether the installer should backup the existing database directory
# and then purge it, or leave it in place. If set to N the installer will fail.
# Used when Puppet Enterprise was uninstalled without the -d option.
#q_backup_and_purge_old_database_directory=y

# String — The git url to be passed to the r10k.yaml file
# This can be any URL that is supported by r10k ( and normally git )
# This answer is OPTIONAL and only needed if you would like r10k configured
# at time of the Puppet Enterprise installation on the master
#q_puppetmaster_r10k_remote='git@your.git.server.com:puppet/control.git'

# String — The local filesystem path on the master where the ssh private key
# can be found and used by r10k. This answer is OPTIONAL and only needed if
# would like r10k configured at time of the Puppet Enterprise installation.
# This must be specified in conjunction with q_puppetmaster_r10k_remote
# to be populated in the configuration file. This will enable rugged
# support in r10k allowing you to use on systems without git installed.
#q_puppetmaster_r10k_private_key=/root/.ssh/id_dsa

# Y or N - Whether or not the file sync service should be enabled on the master
# node.  This will be 'Y' by default for installs and 'N' by default for
# upgrades because migrating an existing codedir to codedir-staging is a manual
# process.  It should only be overridden if you have already made that migration.
#
# NOTE: For split installs, if you set this on your master, you must have the 
# same answer on the console node for correct classification or the changes
# will be overriden during the first puppet run on the master.
#q_puppetmaster_file_sync_service_enabled=

# Y or N - Whether to automatically configure code-manager. This answer is
# OPTIONAL and only needed if you would like code-manager to be configured at
# install time based on r10k answers.
#q_puppetmaster_code_manager_auto_configure=n

#--------------------------------------------------------------------
# Puppet Console Answers
# These answers are generally needed if you are installing the puppet console
# role.

# String — The hostname of the server running the master role. Only needed if
# you are not installing the console role on the puppet master server.
#q_puppet_enterpriseconsole_master_hostname=pe-master.localdomain

# Integer — The port on which to serve the console. The default is port 443,
# which will allow access to the console from a web browser without manually
# specifying a port. If port 443 is not available, the installer will try port
# 3000, 3001, 3002, 3003, 3004, and 3005.
q_puppet_enterpriseconsole_httpd_port=443

# String — The password for the console’s admin user. Must be longer than eight
# characters.
q_puppet_enterpriseconsole_auth_password=strongpassword2536

# String — A publicly accessible hostname where the console can be accessed if
# the host name resolves to a private interface (e.g., Amazon EC2). This is set
# automatically by the installer on EC2 nodes, but can be set manually in
# environments with multiple hostnames.
#q_public_hostname=

#--------------------------------------------------------------------
# Database Support Answers
# These answers are only needed if you are installing the database support
# role.

# Y or N — Whether or not to install the PostgreSQL server that supports the
# console.
q_database_install=y

# String - The hostname of the PostgreSQL server.
q_database_host=pe-puppet.localdomain

# String - The port of the PostgreSQL server.
q_database_port=5432

# String - PostgreSQL server's root user name.
q_database_root_user=pe-postgres

# String — The password for PostgreSQL’s root user.
q_database_root_password=strongpassword8721

# String - The database orchestrator will use.
q_orchestrator_database_name=pe-orchestrator

# String - The password for Orchestrator's root user.
q_orchestrator_database_password=strongpassword9285

# String - Orchestator’s root user name
q_orchestrator_database_user=pe-orchestrator

# String — The database PuppetDB will use.
q_puppetdb_database_name=pe-puppetdb

# String — The password for PuppetDB’s root user.
q_puppetdb_database_password=strongpassword1748

# String — PuppetDB’s root user name.
q_puppetdb_database_user=pe-puppetdb

# String — The hostname of the server running PuppetDB.
#q_puppetdb_hostname=pe-puppet.localdomain

# Integer — The port where the PuppetDB server can be reached.
#q_puppetdb_port=8081

# Integer -  The port on which PuppetDB accepts plain-text HTTP connections (default port is 8080).
#q_puppetdb_plaintext_port=8080

# String — The database RBAC will use.
q_rbac_database_name=pe-rbac

# String — The password for RBAC's root user.
q_rbac_database_password=strongpassword8044

# String — RBAC’s root user name.
q_rbac_database_user=pe-rbac

# String — The database classifier will use.
q_classifier_database_name=pe-classifier

# String — The password for classifier's root user.
q_classifier_database_password=strongpassword1744

# String — classifier’s root user name.
q_classifier_database_user=pe-classifier

# String — The database activity service will use.
q_activity_database_name=pe-activity

# String — The password for activity service 's root user.
q_activity_database_password=strongpassword9972

# String — activity service’s root user name.
q_activity_database_user=pe-activity

#--------------------------------------------------------------------
# Upgrader Answers
# These answers are only needed if you are upgrading.

# Y or N — Used when upgrading and the amount of disk space available appears to
# be too low for the database to be converted. This can be a false alarm at
# times if the dataabse has not been vacuumed. If N the install will fail.
#q_upgrade_with_low_disk_space=n

# Y or N — Used when upgrading and the amount of disk space available cannot be determined. If N the install will fail.
#q_upgrade_with_unknown_disk_space=n

#--------------------------------------------------------------------
# Uninstaller Answers
# These answers are only needed if you are uninstalling.

# Y or N — Whether to uninstall. Answer files must set this to Y.
#q_pe_uninstall=y

# Y or N — Whether to purge additional files when uninstalling, including all
# configuration files, modules, manifests, certificates, and the home directories
# of any users created by the PE installer.
#q_pe_purge=y

# Y or N — Whether to remove any PE-specific databases when uninstalling.
#q_pe_remove_db=y

# Whether to exit the installer (during upgrade) to perform the NC Data Migration process
# See http://docs.puppetlabs.com/pe/3.8/install_upgrade_migration_tool.html

q_exit_for_nc_migrate=n
