Assembler Subscription. How to access parameters for an event and input for a deployment.

[Michael Cornn]

1. In Assembler event subscriptions, how can the action access the event parameters?
2. For subscriptions to compute.provision. and deployment. events, can the action view (or change) the input parameters?

In Assembler, I created two Subscriptions. The first is subscribed to compute.provision.pre and the second to deployment.request.post. 

We have a template that deploys a VM. Here's the YAML for the template:

formatVersion: 1
inputs:
  dataCenter:
    type: string
    title: Data Center
    description: Data Center in which to deploy the VM.
    default: d1
    enum:
      - c1
      - d1
    vmSize:
        type: string
        description: CPU and RAM requirement
        default: 2CPU/8RAM
        enum:
          - 2CPU/8RAM
          - 4CPU/16RAM
          - 8CPU/32RAM
resources:
  Windows Server:
    type: Cloud.vSphere.Machine
    properties:
      image: ${input.dataCenter}-server
      flavor: ${input.vmSize}
      name: ${input.dataCenter}-newhostname
      constraints:
        - tag: ${input.dataCenter}

When we deploy from this template, the actions in the subscriptions fire correctly. However, we want the actions to view and modify both the event parameters as well as the doployment input. 

If we use PowerShell to code the action, what's the variable name for those parameters?

-------------------------------------------

[kjellcomputer]

Hi, with Actions I assume ABX Actions?

If you look at the Event Topic for compute.allocation.pre you will see the variable name for the parameters and which can be viewed and updated:


Your output would need to be this parameter name for it to be updated (one or many). An example to update the value for the parameter 'image' with ABX Action using Powershell can be:

[PSCustomObject]@{
    image = 'Ubuntu'
}

The parameters are in the automatic variable $inputs, so to view the value for image it will be $inputs.image

To view deployment input's you would need to implement REST-calls from your powershell-action against the /deployment/api/deployments/{id} uri. And your deployment Id is in $inputs.deploymentId.

-------------------------------------------