projectatomic/atomic
1
0
Fork 0
mirror of https://github.com/projectatomic/atomic.git synced 2026-02-05 18:45:01 +01:00
Code Issues Releases Activity
Files
master
atomic/atomic.conf

27 lines
617 B
Plaintext
Raw Permalink Normal View History

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
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
Honor proxy usage If HTTP[S]_PROXY is defined, honor it in python requests usage as well as pass it on to skopeo. If http[s]_proxy is defined in atomic.conf, use it; however, environment variables will override these if defined. Added --insecure to Atomic push so the user can override the logic (or lack thereof) around deducing if a registry is insecure. Also needed for integration tests. Closes: #964 Approved by: rhatdan
2017-04-03 13:50:40 -05:00
#
# To always use a proxy with atomic, you can uncomment and fill out
# below.
#
atomic.conf: fix syntax error of the YAML format We use YAML format in atomic.conf file, so it should be KEY: VALUE not KEY=VALUE. Signed-off-by: Alex Jia <ajia@redhat.com> Closes: #1004 Approved by: baude
2017-05-17 11:37:13 +08:00
#http_proxy:
#https_proxy:
#no_proxy:
Copy Permalink