tag/list/atomic.conf

# Atomic CLI configuration file

default_scanner:
default_docker: docker
registry_confdir: /etc/containers/registries.d/
discover_sigstores: true
sigstore_metadata_image: sigstore
pubkeys_dir: /etc/pki/containers


# Default storage backend [ostree, docker]
# default_storage: docker
# ostree_repository: /ostree/repo
# checkout_path: /var/lib/containers/atomic
#

# Default identity for signing images
# default_signer:
# Absolute path to GPG keyring. Value set as environment variable GNUPGHOME
#gnupg_homedir: /home/USER/.gnupg
Implement generic scanning in Atomic As more scanners besides openscap become available, atomic can now begin to leverage them. The new scan function has been broken out into its on file (scan.py). The scan command itself now defaults to openscap but can also be switched to blackduck with --scanner. Atomic now can use a configuration file which is stored in /etc/atomic.conf. The location of the atomic conf file can be overriden with the environment variable 'ATOMIC_CONF'. In the case of the scan function, we need the scanner defined in the configuration file as well as the fully qualified image name and the scan arguments. Optionally, you can provide additional custom docker arguments for the scanner as well 2016-02-25 17:07:24 -06:00			`# Atomic CLI configuration file`

Change rules around declaring a default scanner. Previously, with the understanding we would be shipping a single generic scanner configuration file, would 1) install the config file and we had preset a default scanner in atomic.conf. With the realization that the scanner could be variable based on the distribution, the generic file is not longer installed by default. Therefore, we should probably not set a default. The prior code failed if a default was not defined in /etc/atomic.conf. That code check has been altered and we now adhere to the following rules: * If no default is defined AND there is only one configured scanner, we assume the single scanner IS the default. * If no default is defined AND there are multiple scanners, we error out and ask the user to define one. * If there is a default defined, good to go! Closes: #383 Approved by: rhatdan 2016-05-12 15:20:54 -05:00			`default_scanner:`
Allow user to specify alternative docker executables. This will allow us to support docker-latest 2016-04-13 08:42:15 -04:00			`default_docker: docker`
Atomic/sign.py\|util.py Support sigstore from conf files We now derive the proper sigstore from a series of YAML configuration files in /etc/containers/registries.d. These configuration files can have: sigstore and sigstore-write as keys and the values are a file path or http\|s URL. When signing an image, as long as the -d override is not used, we use those values when writing local signatures. Closes: #603 Approved by: rhatdan 2016-09-09 09:52:06 -05:00			`registry_confdir: /etc/containers/registries.d/`
signing bootstrap workflow Closes: #599 Approved by: rhatdan 2016-09-08 17:12:27 -04:00			`discover_sigstores: true`
			`sigstore_metadata_image: sigstore`
			`pubkeys_dir: /etc/pki/containers`
Implement generic scanning in Atomic As more scanners besides openscap become available, atomic can now begin to leverage them. The new scan function has been broken out into its on file (scan.py). The scan command itself now defaults to openscap but can also be switched to blackduck with --scanner. Atomic now can use a configuration file which is stored in /etc/atomic.conf. The location of the atomic conf file can be overriden with the environment variable 'ATOMIC_CONF'. In the case of the scan function, we need the scanner defined in the configuration file as well as the fully qualified image name and the scan arguments. Optionally, you can provide additional custom docker arguments for the scanner as well 2016-02-25 17:07:24 -06:00
Atomic/sign.py\|util.py Support sigstore from conf files We now derive the proper sigstore from a series of YAML configuration files in /etc/containers/registries.d. These configuration files can have: sigstore and sigstore-write as keys and the values are a file path or http\|s URL. When signing an image, as long as the -d override is not used, we use those values when writing local signatures. Closes: #603 Approved by: rhatdan 2016-09-09 09:52:06 -05:00
			`# Default storage backend [ostree, docker]`
Atomic/pull.py: Set docker as default backend Setting docker as the default backend instead of ostree. Closes: #637 Approved by: rhatdan 2016-09-20 07:53:08 -05:00			`# default_storage: docker`
atomic.conf: Add option to configure the OSTree repository Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com> 2016-04-11 12:27:53 +02:00			`# ostree_repository: /ostree/repo`
atomic.conf: Add option to configure the checkout path Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com> 2016-04-11 12:30:10 +02:00			`# checkout_path: /var/lib/containers/atomic`
Atomic/sign.py\|util.py Support sigstore from conf files We now derive the proper sigstore from a series of YAML configuration files in /etc/containers/registries.d. These configuration files can have: sigstore and sigstore-write as keys and the values are a file path or http\|s URL. When signing an image, as long as the -d override is not used, we use those values when writing local signatures. Closes: #603 Approved by: rhatdan 2016-09-09 09:52:06 -05:00			`#`

			`# Default identity for signing images`
			`# default_signer:`
add keyring override config Closes: #643 Approved by: rhatdan 2016-09-21 10:26:38 -04:00			`# Absolute path to GPG keyring. Value set as environment variable GNUPGHOME`
			`#gnupg_homedir: /home/USER/.gnupg`