To update the application configuration using the yaml file, follow these steps:
Copy the template yaml file.
cd $JFROG_HOME/distribution/var/etc/distribution/ cp template.distribution.config.import.yml distribution.config.import.yml
A snapshot of the last imported configuration state will be saved as
Previous yaml configuration files will be saved as
task: heartbeat: interval-seconds: 5 # interval between successive runs of the heartbeat job consider-stale-seconds: 30 # the time period (seconds) a server can remain unresponsive before being considered stale in the cluster distribute: interval-seconds: 5 # interval between successive runs of the distribute job releaseBundleHandler: interval-seconds: 5 # interval between successive runs of the release bundle handler job cluster: sync: timeout-millis: 100 # initial time (ms) to wait before retrying a request socket-timeout-millis: 5000 # time to wait (ms) before giving up on executing a REST call on another server exponential-backoff-multiplier: 2 # number by which the retry timeout should be multiplied before a subsequent retry. For example, by default, the third retry will happen after 200 ms number-of-retries: 3 # maximum number of retries backoff-max-delay-millis: 1000 # maximum time between successive retries regardless of other settings call-home: enabled: true release-bundle: max-artifacts: 3000 # maximum number of artifacts to fetch from artifactory on release bundle creation distribute: edge-node-token-expiration-minutes: 180 # the time period (minutes) a token lives for communicating with edge node load-balancer: "simple" # algorithm to use for distributing the work between the Distribution nodes server: max-http-header-size: 16384 # 16kb in bytes artifactory-client: client-short-socket-timeout: 10000 # socket timeout in millis for Artifactory bound short tasks, e.g.: auth and pairing with Artifactory client-long-socket-timeout: 120000 # socket timeout in millis for Artifactory bound long tasks, e.g.: release-bundles' store, deletion and artifacts' gathering (AQL) queries xray: release-bundle-scan-consider-stuck: 600000 # the time in millis for xray vulnerability scanning considering stuck
The Request header max size can manually be increased to prevent receiving an HTTP 400 message when signing into Distribution with SSO.
Distribution will trigger the source Artifactory to clone the contents of signed release bundles into an isolated
release-bundles repository. To allow this, you need to deploy the GPG Key that is used in each of your Artifactory Edge nodes to the source Artifactory service.
For more details, refer to Setting a GPG Key.
For more details on additional required configurations, refer to configuring Distribution.