Minor changes

[khalford]

Minor changes to the deployment.

• Fixes a typo with the SSL role module task name
• Removes unused count variable from container name
• Rotate secrets
• Add terraform variable to use separate clouds.yaml entries for authenticating against multiple clouds

[jose-caballero]

I have a question:

On the new variable for clouds.yaml, why is it called "openstack"? Is that required by terraform? I find the name "openstack" to be a little bit ambiguous, can be interpreted in many different ways, so I would suggest something more clear unless we are forced to used it.

[khalford]

I have a question:

On the new variable for clouds.yaml, why is it called "openstack"? Is that required by terraform? I find the name "openstack" to be a little bit ambiguous, can be interpreted in many different ways, so I would suggest something more clear unless we are forced to used it.

I understand it is weird. I was just using whatever name the clouds.yaml file suggests to use. But actually I remembered incorrectly.

# This is a clouds.yaml file, which can be used by OpenStack tools as a source
# of configuration on how to connect to a cloud. If this is your only cloud,
# just put this file in ~/.config/openstack/clouds.yaml and tools like
# python-openstackclient will just work with no further config. (You will need
# to add your password to the auth section)
# If you have more than one cloud account, add the cloud entry to the clouds
# section of your existing file and you can refer to them by name with
# OS_CLOUD=openstack or --os-cloud=openstack
clouds:

I will rename it from openstack -> cloud

[jose-caballero]

Does that mean that Terraform is not capable of getting the cloud name from the title of each section in clouds.yaml, and that's why you need to add another label to the file?

[jose-caballero]

I can reply to my last question. Apparently not, from what Gemini just told me :)