rhsm_register Resource
This page is generated from the Chef Infra Client source code.To suggest a change, edit the rhsm_register.rb file and submit a pull request to the Chef Infra Client repository.
Use the rhsm_register resource to register a node with the Red Hat Subscription Manager or a local Red Hat Satellite server.
New in Chef Infra Client 14.0.
Syntax
The full syntax for all of the properties that are available to the rhsm_register resource is:
rhsm_register 'name' do
activation_key String, Array
auto_attach true, false # default value: false
base_url String
environment String
force true, false # default value: false
https_for_ca_consumer true, false # default value: false
install_katello_agent true, false # default value: true
organization String
password String
release Float, String
satellite_host String
server_url String
service_level String
system_name String
username String
action Symbol # defaults to :register if not specified
end
where:
rhsm_register
is the resource.name
is the name given to the resource block.action
identifies which steps Chef Infra Client will take to bring the node into the desired state.activation_key
,auto_attach
,base_url
,environment
,force
,https_for_ca_consumer
,install_katello_agent
,organization
,password
,release
,satellite_host
,server_url
,service_level
,system_name
, andusername
are the properties available to this resource.
Actions
The rhsm_register resource has the following actions:
:nothing
- This resource block does not act unless notified by another resource to take action. Once notified, this resource block either runs immediately or is queued up to run at the end of a Chef Infra Client run.
:register
- Register the node with RHSM. (default)
:unregister
- Unregister the node from RHSM.
Properties
The rhsm_register resource has the following properties:
activation_key
- Ruby Type: String, Array
A string or array of activation keys to use when registering; you must also specify the ‘organization’ property when using this property.
auto_attach
- Ruby Type: true, false | Default Value:
false
If true, RHSM will attempt to automatically attach the host to applicable subscriptions. It is generally better to use an activation key with the subscriptions pre-defined.
base_url
- Ruby Type: String
The hostname of the content delivery server to use to receive updates. Both Customer Portal Subscription Management and Subscription Asset Manager use Red Hat’s hosted content delivery services, with the URL https://cdn.redhat.com. Since Satellite 6 hosts its own content, the URL must be used for systems registered with Satellite 6.
New in Chef Infra Client 17.8
environment
- Ruby Type: String
The environment to use when registering; required when using the username and password properties.
force
- Ruby Type: true, false | Default Value:
false
If true, the system will be registered even if it is already registered. Normally, any register operations will fail if the machine has already been registered.
https_for_ca_consumer
- Ruby Type: true, false | Default Value:
false
If true, Chef Infra Client will fetch the katello-ca-consumer-latest.noarch.rpm from the satellite_host using HTTPS.
New in Chef Infra Client 15.9
install_katello_agent
- Ruby Type: true, false | Default Value:
true
If true, the ‘katello-agent’ RPM will be installed.
organization
- Ruby Type: String
The organization to use when registering; required when using the ‘activation_key’ property.
password
- Ruby Type: String
The password to use when registering. This property is not applicable if using an activation key. If specified, username and environment are also required.
release
- Ruby Type: Float, String
Sets the operating system minor release to use for subscriptions for the system. Products and updates are limited to the specified minor release version. This is used with the
auto_attach
oractivation_key
options. For example,release '6.4'
will append--release=6.4
to the register command.New in Chef Infra Client 17.8
satellite_host
- Ruby Type: String
The FQDN of the Satellite host to register with. If this property is not specified, the host will register with Red Hat’s public RHSM service.
server_url
- Ruby Type: String
The hostname of the subscription service to use. The default is Customer Portal Subscription Management, subscription.rhn.redhat.com. If you do not use this option, the system registers with Customer Portal Subscription Management.
New in Chef Infra Client 17.8
service_level
- Ruby Type: String
Sets the service level to use for subscriptions on the registering machine. This is only used with the
auto_attach
option.New in Chef Infra Client 17.8
system_name
- Ruby Type: String
The name of the system to register, defaults to the hostname.
New in Chef Infra Client 16.5
username
- Ruby Type: String
The username to use when registering. This property is not applicable if using an activation key. If specified, password and environment properties are also required.
Common Resource Functionality
Chef resources include common properties, notifications, and resource guards.
Common Properties
The following properties are common to every resource:
compile_time
Ruby Type: true, false | Default Value:
false
Control the phase during which the resource is run on the node. Set to true to run while the resource collection is being built (the
compile phase
). Set to false to run while Chef Infra Client is configuring the node (theconverge phase
).ignore_failure
Ruby Type: true, false, :quiet | Default Value:
false
Continue running a recipe if a resource fails for any reason.
:quiet
will not display the full stack trace and the recipe will continue to run if a resource fails.retries
Ruby Type: Integer | Default Value:
0
The number of attempts to catch exceptions and retry the resource.
retry_delay
Ruby Type: Integer | Default Value:
2
The delay in seconds between retry attempts.
sensitive
Ruby Type: true, false | Default Value:
false
Ensure that sensitive resource data is not logged by Chef Infra Client.
Notifications
notifies
Ruby Type: Symbol, 'Chef::Resource[String]'
A resource may notify another resource to take action when its state changes. Specify a
'resource[name]'
, the:action
that resource should take, and then the:timer
for that action. A resource may notify more than one resource; use anotifies
statement for each resource to be notified.If the referenced resource does not exist, an error is raised. In contrast,
subscribes
will not fail if the source resource is not found.
A timer specifies the point during a Chef Infra Client run at which a notification is run. The following timers are available:
:before
Specifies that the action on a notified resource should be run before processing the resource block in which the notification is located.
:delayed
Default. Specifies that a notification should be queued up, and then executed at the end of a Chef Infra Client run.
:immediate
,:immediately
Specifies that a notification should be run immediately, for each resource notified.
The syntax for notifies
is:
notifies :action, 'resource[name]', :timer
subscribes
Ruby Type: Symbol, 'Chef::Resource[String]'
A resource may listen to another resource, and then take action if the
state of the resource being listened to changes. Specify a
'resource[name]'
, the :action
to be taken, and then the :timer
for
that action.
Note that subscribes
does not apply the specified action to the
resource that it listens to - for example:
file '/etc/nginx/ssl/example.crt' do
mode '0600'
owner 'root'
end
service 'nginx' do
subscribes :reload, 'file[/etc/nginx/ssl/example.crt]', :immediately
end
In this case the subscribes
property reloads the nginx
service
whenever its certificate file, located under
/etc/nginx/ssl/example.crt
, is updated. subscribes
does not make any
changes to the certificate file itself, it merely listens for a change
to the file, and executes the :reload
action for its resource (in this
example nginx
) when a change is detected.
If the other resource does not exist, the subscription will not raise an
error. Contrast this with the stricter semantics of notifies
, which
will raise an error if the other resource does not exist.
A timer specifies the point during a Chef Infra Client run at which a notification is run. The following timers are available:
:before
Specifies that the action on a notified resource should be run before processing the resource block in which the notification is located.
:delayed
Default. Specifies that a notification should be queued up, and then executed at the end of a Chef Infra Client run.
:immediate
,:immediately
Specifies that a notification should be run immediately, for each resource notified.
The syntax for subscribes
is:
subscribes :action, 'resource[name]', :timer
Guards
A guard property can be used to evaluate the state of a node during the execution phase of a Chef Infra Client run. Based on the results of this evaluation, a guard property is then used to tell Chef Infra Client if it should continue executing a resource. A guard property accepts either a string value or a Ruby block value:
- A string is executed as a shell command. If the command returns
0
, the guard is applied. If the command returns any other value, then the guard property is not applied. String guards in a powershell_script run Windows PowerShell commands and may returntrue
in addition to0
. - A block is executed as Ruby code that must return either
true
orfalse
. If the block returnstrue
, the guard property is applied. If the block returnsfalse
, the guard property is not applied.
A guard property is useful for ensuring that a resource is idempotent by allowing that resource to test for the desired state as it is being executed, and then if the desired state is present, for Chef Infra Client to do nothing.
PropertiesThe following properties can be used to define a guard that is evaluated during the execution phase of a Chef Infra Client run:
not_if
Prevent a resource from executing when the condition returns
true
.only_if
Allow a resource to execute only if the condition returns
true
.
Examples
The following examples demonstrate various approaches for using the rhsm_register resource in recipes:
Register a node with RHSM
rhsm_register 'my-host' do
activation_key 'ABCD1234'
organization 'my_org'
end