ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Tasks with Environment fields

book

Article ID: 213857

calendar_today

Updated On:

Products

Continuous Delivery Director

Issue/Introduction

In case I setup the phase to development environment I can still trigger a deployment to production environment nothing prevents me to define production environment to target environment in Nolio plugin. Is this intentional?

To workaround this we did not come up with anything that having 2 endpoints where the other has access to production environments and the other has access to development environments. If then adding the remote application on both endpoints it will create duplicate applications.

 

Example:

The Phase has been set to execute against the Env1 environment. However, in the Run Deployment Nolio task we can run it against the Env2 environment. 

 

Environment

Release : 8.0.0

Component : CDD RELEASE DESIGN & EXECUTION

Resolution

CDD can only limit the usage of a specific endpoint in a specific environment. If the endpoint allows deployment in other environments, CDD cannot enforce it. The endpoint user can be limited to the environment. For example, if the user used by the Endpoint does not have access to Env2 (in Nolio) then the task fails - as shown below:

 

 

 

 

Additional Information

It is considered best practice to setup tasks that have input fields targeting Environments to utilize the %cdd.phase_environment token. 

 

Attachments