actions-marketplace-validations/ansible-playbook-with-keyvault

Execute an ansible playbook with credentials held in keyvault

Trust Signals

name	description	required	default
azure_creds	If azure login required, the secret containing azure credentials, i.e. output of `az ad sp create-for-rbac`	no	—
keyvault_name	Name of the azure key vault	no	—
keyvault_secret_name_ssh_password	The name of the key vault secret that holds the ssh password	no	—
keyvault_secret_name_vault_password	The name of the key vault secret that holds the ansible vault password	no	—
keyvault_secret_name_ssh_privkey	The name of the key vault secret that holds the ssh private key	no	—
ssh_password_txt_filename	Optional txt filename to write the ssh password to	no	ansible_pass
ssh_privkey_filename	The filename to write the ssh private key to	no	ansible_key
vault_password_filename	The filename to write the vault password to	—	.vault.txt
extra_vars_yaml_filename	The yaml filename to write extra variables to	—	extravars.yaml
ansible_dir	Directory containing ansible code	yes	—
ansible_playbook	Location of ansible playbook	yes	—
ansible_inventory	Location of ansible inventory	no	—
ansible_limit	Optionally limit to comma separated set of hosts or targets	no	—
ansible_user	The username to use for -u, remote_user, ansible_user options	no	—
ansible_vars	Pipe separated additional variables to pass in as -e option (via yamlfile), e.g. "foo=bar\|abc=def"	no	—
ansible_args	Pipe separated ansible args e,g, "--verbose\|--check\|--foo bar	no	—
ansible_config	Location of ansible config	no	—
action_settings	For debugging the action, e.g. showCliOutput,hideAnsibleOutput,noCleanup,noAnsible	no	—

no outputs