Episode 6 - Ansible Vault and Roles (April 29) Episode 7 - Ansible Galaxy, ansible-lint, and Molecule testing (May 6) Episode 8 - Testing Ansible playbooks with Molecule and GitHub Actions for CI (May 13) Episode 9 - First 5 minutes server security with Ansible (May 20) Episode 10 - Ansible Tower and AWX (May 27) New in Ansible 1.5, “Vault” is a feature of ansible that allows keeping sensitive data such as passwords or keys in encrypted files, rather than as plaintext in your playbooks or roles. These vault files can then be distributed or placed in source control. To enable this feature, a command line tool, ansible-vault is used to edit files, and a command line flag –ask-vault-pass or –vault-password-file is used. The following plugin provides functionality available through Pipeline-compatible steps. Read more about how to integrate steps into your Pipeline in the Steps section of the Pipeline Syntax page. Since Ansible 2.4, there is support for having multiple vault IDs, thus different security levels can be isolated. For instance, developers would not have access to the production secrets. As for distribution, scripts can be used as a vault password file so vault passwords can be encrypted with people’s GPG keys and securely distributed. key - (Required) The public SSH key to add to your GitHub account. » Attributes Reference The following attributes are exported: id - The ID of the SSH key url - The URL of the SSH key » Import SSH keys can be imported using their ID e.g.