When passing Encrypted Aria Automation inputs to SaltStack Element variables the property values are not decrypted
search cancel

When passing Encrypted Aria Automation inputs to SaltStack Element variables the property values are not decrypted

book

Article ID: 314903

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

Symptoms:
  • When passing Encrypted Aria Automation inputs to SaltStack Element variables the property values are not decrypted. If you have an encrypted input in your Aria Automation blueprint, see example below which uses an encrypted password input:
password:
type: string
title: Admin Password
pattern: '[a-z0-9A-Z@#$]+'
encrypted: true

and the value is passed to a salt stack element variable:
 
 SaltStack:
 type: Cloud.SaltStack
 properties:
 hosts:
${resource.OpenCart.id}
masterId: saltstack_enterprise_installer
saltEnvironment: sse
stateFiles:
${input.osType == "Linux" ? "/motd/init.sls" :"/none/init.sls"}
${input.statefiles}
variables:
user: ${input.username}
pass: ${input.password}

 
The password value is not decrypted in Aria Automation before its passed to the pass property under variables in SaltStack. When retrieving the value from the pillar to the state file the password is still encrypted.


Environment

VMware Aria Automation 8.x
VMware Aria Automation Config 8.x

Resolution

There is currently no resolution available for the issue. The functionality to pass encrypted property values between Aria Automation and Aria Automation Config is being evaluated for inclusion in future releases.