2.40. hammer job-template
Manage job templates
Usage:
hammer job-template [OPTIONS] SUBCOMMAND [ARG] ...
Parameters:
SUBCOMMAND Subcommand
[ARG] ... Subcommand arguments
Subcommands:
create Create a job template
delete, destroy Delete a job template
dump View job template content
export Export a template including all metadata
import Import a job template from ERB
info, show Show job template details
list, index List job templates
update Update a job template
Options:
-h, --help Print help
Usage:
hammer job-template [OPTIONS] SUBCOMMAND [ARG] ...
Parameters:
SUBCOMMAND Subcommand
[ARG] ... Subcommand arguments
Subcommands:
create Create a job template
delete, destroy Delete a job template
dump View job template content
export Export a template including all metadata
import Import a job template from ERB
info, show Show job template details
list, index List job templates
update Update a job template
Options:
-h, --help Print help
2.40.1. hammer job-template create リンクのコピーリンクがクリップボードにコピーされました!
リンクのコピーリンクがクリップボードにコピーされました!
Create a job template
Usage:
hammer job-template create [OPTIONS]
Options:
--audit-comment AUDIT_COMMENT
--current-user CURRENT_USER Whether the current user login should be used as the effective user
One of true/false, yes/no, 1/0.
--description DESCRIPTION
--description-format DESCRIPTION_FORMAT This template is used to generate the description. Input values can be used
Using the syntax %{package}. You may also include the job category and
Template name using %{job_category} and %{template_name}.
--file TEMPLATE Path to a file that contains the template
--job-category JOB_CATEGORY Job category
--location LOCATION_NAME Set the current location context for the request
--location-id LOCATION_ID Set the current location context for the request
--location-ids LOCATION_IDS REPLACE locations with given ids
Comma separated list of values. Values containing comma should be quoted or escaped with backslash.
JSON is acceptable and preferred way for complex parameters
--location-title LOCATION_TITLE Set the current location context for the request
--location-titles LOCATION_TITLES Comma separated list of values. Values containing comma should be quoted or escaped with backslash.
JSON is acceptable and preferred way for complex parameters
--locations LOCATION_NAMES Comma separated list of values. Values containing comma should be quoted or escaped with backslash.
JSON is acceptable and preferred way for complex parameters
--locked LOCKED Whether or not the template is locked for editing
One of true/false, yes/no, 1/0.
--name NAME Template name
--organization ORGANIZATION_NAME Set the current organization context for the request
--organization-id ORGANIZATION_ID Set the current organization context for the request
--organization-ids ORGANIZATION_IDS REPLACE organizations with given ids.
Comma separated list of values. Values containing comma should be quoted or escaped with backslash.
JSON is acceptable and preferred way for complex parameters
--organization-title ORGANIZATION_TITLE Set the current organization context for the request
--organization-titles ORGANIZATION_TITLES Comma separated list of values. Values containing comma should be quoted or escaped with backslash.
JSON is acceptable and preferred way for complex parameters
--organizations ORGANIZATION_NAMES Comma separated list of values. Values containing comma should be quoted or escaped with backslash.
JSON is acceptable and preferred way for complex parameters
--overridable OVERRIDABLE Whether it should be allowed to override the effective user from the
Invocation form.
One of true/false, yes/no, 1/0.
--provider-type PROVIDER_TYPE Provider type
Possible value(s): 'SSH', 'Ansible'
--snippet SNIPPET One of true/false, yes/no, 1/0.
--value VALUE What user should be used to run the script (using sudo-like mechanisms)
-h, --help Print help
Usage:
hammer job-template create [OPTIONS]
Options:
--audit-comment AUDIT_COMMENT
--current-user CURRENT_USER Whether the current user login should be used as the effective user
One of true/false, yes/no, 1/0.
--description DESCRIPTION
--description-format DESCRIPTION_FORMAT This template is used to generate the description. Input values can be used
Using the syntax %{package}. You may also include the job category and
Template name using %{job_category} and %{template_name}.
--file TEMPLATE Path to a file that contains the template
--job-category JOB_CATEGORY Job category
--location LOCATION_NAME Set the current location context for the request
--location-id LOCATION_ID Set the current location context for the request
--location-ids LOCATION_IDS REPLACE locations with given ids
Comma separated list of values. Values containing comma should be quoted or escaped with backslash.
JSON is acceptable and preferred way for complex parameters
--location-title LOCATION_TITLE Set the current location context for the request
--location-titles LOCATION_TITLES Comma separated list of values. Values containing comma should be quoted or escaped with backslash.
JSON is acceptable and preferred way for complex parameters
--locations LOCATION_NAMES Comma separated list of values. Values containing comma should be quoted or escaped with backslash.
JSON is acceptable and preferred way for complex parameters
--locked LOCKED Whether or not the template is locked for editing
One of true/false, yes/no, 1/0.
--name NAME Template name
--organization ORGANIZATION_NAME Set the current organization context for the request
--organization-id ORGANIZATION_ID Set the current organization context for the request
--organization-ids ORGANIZATION_IDS REPLACE organizations with given ids.
Comma separated list of values. Values containing comma should be quoted or escaped with backslash.
JSON is acceptable and preferred way for complex parameters
--organization-title ORGANIZATION_TITLE Set the current organization context for the request
--organization-titles ORGANIZATION_TITLES Comma separated list of values. Values containing comma should be quoted or escaped with backslash.
JSON is acceptable and preferred way for complex parameters
--organizations ORGANIZATION_NAMES Comma separated list of values. Values containing comma should be quoted or escaped with backslash.
JSON is acceptable and preferred way for complex parameters
--overridable OVERRIDABLE Whether it should be allowed to override the effective user from the
Invocation form.
One of true/false, yes/no, 1/0.
--provider-type PROVIDER_TYPE Provider type
Possible value(s): 'SSH', 'Ansible'
--snippet SNIPPET One of true/false, yes/no, 1/0.
--value VALUE What user should be used to run the script (using sudo-like mechanisms)
-h, --help Print help