shield-agent job from shield/6.4.1
Github source:
1fd648a0
or
master branch
Properties¶
shield
¶
agent
¶
autoprovision
¶Optional HTTP API of the Shield installation to automatically provision authorized keys from
daemon_public_key
¶public key to permit access from a shield daemon
ip
¶IP address that the agent can be contacted at. Normally, this can be automatically detected, but for certain circumstances (i.e. bosh-init deployments), you must specify it.
plugin_paths
¶Map of paths that the binary of the plugins can be found
- Example
|+ plugin_paths: atmos: /var/vcap/packages/atmos-plugin/bin
port
¶port to run agent
- Default
5444
recovery
¶
store_config
¶A map of key-values that will be converted to JSON, representing the store plugin configration
store_plugin
¶Store plugin to use in emergency-recovery-mode
target_config
¶A map of key-values that will be converted to JSON, representing the target plugin configration
target_plugin
¶Target plugin to use in emergency-recovery-mode
daemon
¶
domain
¶Hostname/IP SHIELD is accessed with
port
¶port to run daemon (https requests)
- Default
443
jobs
¶A list of Jobs to autoprovision in SHIELD, keyed by name. You can optionally override the name of the job with a ‘name’ attribute. For example: shield: jobs: my-backups: target: localdb store: amazon retention: longterm schedule: weekly
log_level
¶Log level for shield processes
- Default
info
provisioning_key
¶API Key to use when provisioning jobs, or targets. Required if shield.target or shield.job have data
- Default
""
retention-policies
¶A list of Retention policies to autoprovision in SHIELD, keyed by name. For example: shield: retention-policies: Short-term: 90d Long-term: 180d
schedules
¶A list of Schedules to autoprovision in SHIELD, keyed by name. For example: shield: schedules: Daily: daily 4am Weekly: weekly on monday 3am
skip_ssl_verify
¶Boolean to determine if SSL certs will be ignored when provisioning SHIELD data
- Default
true
stores
¶A list of Stores to autoprovision in SHIELD, keyed by name. You can optionally override the name of the store with a ‘name’ attribute. For example: shield: stores: amazon: plugin: s3 config: secret_key: foo bucket: my-backups
targets
¶A list of Targets to autoprovision in SHIELD, keyed by name. You can optionally override the name of the target with a ‘name’ attribute. For example: shield: targets: localdb: plugin: postgres config: pg_host: 10.0.0.6 pg_port: 5524 # etc.
Templates¶
Templates are rendered and placed onto corresponding
instances during the deployment process. This job's templates
will be placed into /var/vcap/jobs/shield-agent/
directory
(learn more).
bin/ctl
(frombin/ctl
)bin/emergency-recovery
(frombin/emergency-recovery
)bin/monit_debugger
(frombin/monit_debugger
)bin/post-start
(frombin/post-start
)config/shield-agent.conf
(fromconfig/shield-agent.conf
)data/properties.sh
(fromdata/properties.sh
)helpers/ctl_setup.sh
(fromhelpers/ctl_setup.sh
)helpers/ctl_utils.sh
(fromhelpers/ctl_utils.sh
)
Packages¶
Packages are compiled and placed onto corresponding
instances during the deployment process. Packages will be
placed into /var/vcap/packages/
directory.