Performing actions on Environments

Environments are created in a couple of different ways and provide rich metadata about how the environment was created and what assets are associated with it. After the environment is created, other actions can be performed on them - for example, Upgrade the application in that environment or Shutdown the environment. 

There are two primary ways to perform an action on an environment:

  1. Environment action task: Creating and executing a task of type "Environment Action".
  2. Using RunApi Plugin in a task: Run API plugin allows you to invoke the CloudMunch REST API and perform actions. Using this plugin in any type of task will enable performing actions on the environment, like changing status etc. More on this here

Environment Action task

Environment Action is one of the categories of the tasks in CloudMunch. This type of task can be executed only on an existing environment regardless of the state of the environment.  

env-action-application-overview

To create an Environment action you can review how a task is created. Environment actions are shown in the action dropdown next to the Environment in the Application Overview page or in the Environment page.

env-action-environment 

When the Environment action is triggered, the trigger action page is shown where you can configure two aspects 

  1. Role: This shows all the Roles that are configured for the application in that environment and the assets associated with each Role. This will allow you to select the assets (example: Servers) that you want to execute the environment action on. For example, you want to execute an environment action that will Upgrade the OS only on the Database Role. So you can select the role and all the Servers associated with the Role
  2. Variables: This will show all the variables that have been configured for the Environment when it was created. You can modify the values as needed for this particular action. 
  3. Steps: This is last configuration aspect of the action. You can select which Steps need to be executed as well as update the configuration for the Step parameters

After the environment action is triggered, you will redirected back to the view from which you triggered the environment. The Environment action appears in the Updated by Task area.