TSA registers workers with the ATC via a SSH interface.
???s with appropriate values.
Following example does not account for release job
collocation or for optional/conflicting properties.
ATC API endpoints to which workers will be advertised. If not specified, they will be autodiscovered via BOSH links.
Permit access via generated worker key, local to the deployment. Set to
falseif you plan on only ever using explicitly configured and authorized worker keys.
Public keys to authorize for SSH connections.
Port on which to listen for SSH connections.
Address to advertise forwarded worker connections to.
If not specified, the instance’s address is used.
Interval on which to register workers with the ATC.
Private key to use for the SSH server. If not specified, a deployment-scoped default is used.
Public key component of the host’s key. This property is exported via the
tsalink so that workers can discover it.
The log level for the TSA.
Public keys to authorize team workers for SSH connections.
|+ - team: concourse ssh_key: ssh-rsa key email@example.com
If configured, errors emitted to the logs will also be emitted to Yeller. This is only really useful for Concourse developers.
Environment name to specify for errors emitted to Yeller.
Templates are rendered and placed onto corresponding
instances during the deployment process. This job's templates
will be placed into
- bin/tsa_ctl (tsa_ctl.erb)
- config/host_key (host_key.erb)