Deployment Parameters

Overview

CloudCenter 4.8.0.1 includes an improvement to allow service parameters to be displayed to end users during deployments. Users can define parameters as deployment parameters and set preferences for them. These preferences govern if the parameters should be visible, editable, and optional during a deployment.

Adding Deployment Parameters

Deployment Parameters are intended to be customized by the user at deployment time and can be created at the service level and used as inherited parameters within an application or directly created when modeling an application.

  • Service-Level Parameters: The parameter is specific to service. If you define a deployment parameter at the service level, then it is displayed as an inherited parameter in the tier where the service is used while modeling an application. You can customize the visibility preferences for this parameter and override the default value when modeling an application.
  • Tier-Level Parameters: The parameter is specific to each step or tier within an application. You can define a deployment parameter at the tier level when modeling an application. You can control the visibility preferences for this parameter during the application modeling process and configure them to be visible, editable, or options during the deployment process.

Using Deployment Parameters

See Using Parameters for additional details.

Inherited Deployment Parameters

If a parameter is defined at the service level, then this parameter displays (inherited) when viewed at the tier level.

These parameters are made available to users that use this service when deploying applications.

When users model applications, these parameters are visible to those using this service. If used at application modeling time, you can only edit the default values for a deployment parameter.

Granular Control for User-Defined Parameters

The following User Options provide granular control over a user-defined parameters:

User OptionCheckedUnchecked
Should this parameter be visible to the user?

This parameter will be visible to users during the application deployment.

Users can override the visibility setting during the application modeling process.

This parameter is not visible to users during the application deployment.
Should this parameter be editable by the user?

This parameter will be editable by users during the application deployment.

Users can override the edit setting during the application modeling process.

This service becomes automatically is disabled for users, and therefore not editable during the application deployment.
Should this parameter be optional?

Marked optional – This parameter will be optional for users during the application deployment.

Users can override the optional setting during the application modeling process.

Marked required – This parameter is requires and the user must provide or select a value during the application deployment.

Allow selection of multiple valuesUsers can select multiple values for this parameter during the application deployment.Users can select one value for this parameter during the application deployment.

Deployment Parameters Icons

Depending on the parameter ownership and permitted actions, you have one of four action icons that you can use at the tier level and at the service level.

  • Click the + icon to add a new Deployment Parameter – at the required point (before or after some other parameter).
  • Click the ↑ arrows to move the priority of the parameter further down in the the order of the listed parameters.
  • Click the ↓ arrow to move the priority of the parameter further down in the the order of the listed parameters.
  • Click the - icon to delete an existing Deployment Parameter.

Deleting Deployment Parameters

If a deployment parameter is deleted at the service level, then all usage for this parameter is impacted – this deployment parameter will not be available when:

  • You edit an application containing that service.
  • Users deploy an application containing that service.

Editing Deployment Parameters

If the default value for a deployment parameter is changed at the service level, then this change reflects in the usage for this parameter at the application level IF the default value was not overridden during the application modeling process.

 

 

 

 

  • No labels