at 16:40 you're looking into why there's an "_" prefix in the output. It's because within keyed_groups you can specify a prefix example: "os". The output of your groups will be "os_redhat" or "os_ubuntu". On the command line if you run ansible -m ping os_redhat it'll target that specific group keyed_groups: - key: tags.OS prefix: "os"
Hi, are you familiar with setting up the same in Tower/Controller? Can a standalone inventory be set up like this, using a source control repo as its... source?
You can configure dynamic inventories in tower / controller. It’s been a hot minute since Iv done it, but it is possible, but there is documentation for it.
@@TheSudo Hi, yes, after creating an Azure Resource Manager type credential and inventory, it all went smoothly. However, I'm using the Ansible Automation Platform 2.1 (AAP). As the environment is container-based, I'm still interested in a CLI setup, just for the sake of argument and knowledge. The container won't see the .azure directory in your Ansible users's home, so a credential file is out of the question (at least as far as I know). Adding credentials to the *azure_rm.yml is not good either, as I don't want to push credentials to Bitbucket. Creating system variables doesn't work, either. And lastly, I seem to remember that the inventory command doesn't work with a vault. So, it would be interesting to know how I would set up the same inventory plugin in CLI with AAP. :)
Hey Niharika, you can create those public keys using the ssh-keygen command and following the prompts. The group_vars file in the Ansible files describes the full path to the key once you have created it and placed it in a directory.
