resource-yaml-v13 - describes the Rundeck resource model document Yaml format
resource YAML document declares a resource model used by a Rundeck Project to define the set of Nodes that are available.
See http://yaml.org for more information about YAML.
In the second case, the
nodename entry is not required.
A Node definition consists of a Map with some required and some optional entries.
Name of the node, this must be a unique Identifier across nodes within a project
Hostname of the node. This can be any IP Address or hostname to address the node. Since hostname is used to make SSH connections, it is possible to overload the value to include port number. (eg, hostname:port).
User name to connect to the node via SSH.
A description of the Node
A literal with comma-separated tag strings, or a Sequence of literals. Tags are used for filtering nodes and often represent server role, environment, class, or group.
URL to an external resource model service.
URL to an external resource model editor service.
Specify any custom attributes about node using a string value.
remoteUrlsee the Rundeck User Manual.
Here’s a node, Venkman.local, described with several of the required and optional attributes discussed above.
Tags are very useful for node filtering and can be used to describe the role, environment, group, or class to which a node belongs. The Homestar.local example below describes a node that plays the role of a redis server in the production environment.
Here’s a node, bartholemew, that specifies some custom attributes (app-port, https-port):
Here is the same two nodes but in the sequence style syntax:
- Homestar.local: description: The production redis server. hostname: Homestar.local nodename: Homestar.local tags: 'redis_server,production' username: greg - bartholemew: description: Webapp node hostname: bartholemew nodename: bartholemew tags: 'web,app' username: greg app-port: 8080 https-port: 8443
The Rundeck source code and all documentation may be downloaded from https://github.com/rundeck/rundeck/.