jumpbox job from jumpbox/4.13.0
Github source:
fd00dff
or
master branch
Properties¶
jumpbox
¶
banner
¶A login banner, or MoTD, to display to users when they log in
- Default
nil
bashrc
¶Additional bash startup commands, to be included verbatim in the system-wide configuration. This can be used to provide additional conveniences or implement site-wide policy.
- Default
""
delete
¶A list of users to delete, specified via account name. By default, users that are removed from the BOSH deployment manifest will be deactivated on the jumpbox deployment, but their files will be retained for reference / forensics.
- Default
[]
env
¶Additional environment variables to set for all users, as well as the start up scripts. This can be used for setting site-wide HTTP proxy configuration. Specified as a map of NAME: VALUE
- Default
{}
hostname
¶Hostname to set on the jumpbox
- Default
jumpbox.local
hosts
¶A list of entries to append to /etc/hosts
- Default
[]
one_time_setup
¶Send new users through a one-time setup. You generally want to do this.
- Default
true
setup
¶
enabled
¶enable or disbale the setup that will install rvm (only disable this if you don’t have internet access)
- Default
true
ssh
¶
allow_agent_forwarding
¶Configure SSHD to allow agent forwarding.
- Default
true
allow_tcp_forwarding
¶Configure SSHD to allow TCP forwarding.
- Default
true
password_auth
¶Configure SSHD to allow users to authenticate via passwords when using SSH.
- Default
false
users
¶List of users to create - name: jhunt shell: /bin/bash env: https://github.com/jhunt/devbox-env.git # specifies a git environment to clone ssh_keys: - ssh-rsa AAAAB3NzaC1yabcd - ssh-rsa AAAAB3NzaC1y1234
- Default
[]
Templates¶
Templates are rendered and placed onto corresponding
instances during the deployment process. This job's templates
will be placed into /var/vcap/jobs/jumpbox/
directory
(learn more).
bin/jumpbox_ctl
(frombin/jumpbox_ctl
)bin/watcher
(frombin/watcher
)config/banner
(fromconfig/banner
)config/bashrc
(fromconfig/bashrc
)
Packages¶
Packages are compiled and placed onto corresponding
instances during the deployment process. Packages will be
placed into /var/vcap/packages/
directory.