From db61b37345086eacf7e997a1b5a3335368fdd313 Mon Sep 17 00:00:00 2001 From: Steven Hardy Date: Mon, 19 Feb 2018 12:02:59 +0000 Subject: [PATCH] Add RHELRegistrationActions to rhel-registration template This can be used in the case where e.g a satellite has been added after the initial deployment to re-register the nodes with the satellite, even those nodes that already exist. Change-Id: I944bc4c65b08de1ca08dd91f55764ebfe141dd9c --- .../pre_deploy/rhel-registration/rhel-registration.yaml | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/extraconfig/pre_deploy/rhel-registration/rhel-registration.yaml b/extraconfig/pre_deploy/rhel-registration/rhel-registration.yaml index adf748df20..1d7dee798e 100644 --- a/extraconfig/pre_deploy/rhel-registration/rhel-registration.yaml +++ b/extraconfig/pre_deploy/rhel-registration/rhel-registration.yaml @@ -65,6 +65,11 @@ parameters: description: | When true, the system profile will be deleted from the registration service when the rhel-registration.yaml nested stack is deleted. + RHELRegistrationActions: + type: comma_delimited_list + default: + - CREATE + description: Actions when the system profile will be registered, by default we only do this on CREATE of a new server, not for existing nodes. conditions: unregister_on_delete: @@ -119,7 +124,7 @@ resources: name: RHELRegistrationDeployment server: {get_param: server} config: {get_resource: RHELRegistration} - actions: ['CREATE'] # Only do this on CREATE + actions: {get_param: RHELRegistrationActions} input_values: REG_ACTIVATION_KEY: {get_param: rhel_reg_activation_key} REG_AUTO_ATTACH: {get_param: rhel_reg_auto_attach} @@ -202,7 +207,7 @@ resources: name: UpdateDeploymentAfterRHELRegistration config: {get_resource: YumUpdateConfigurationAfterRHELRegistration} server: {get_param: server} - actions: ['CREATE'] # Only do this on CREATE + actions: {get_param: RHELRegistrationActions} outputs: deploy_stdout: