Allow OpenStack API authentication information used by Terraform OpenStack provider to be different to OpenStack API application credential used by deployed CitC instance.
The application credential to be used by the deployed CitC is provided in a clouds.yaml file specified using the clouds_yaml Terraform variable. OpenStack API authentication for Terraform OpenStack provider can be separate to this, e.g. using a user/system clouds.yaml and cloud specified by environment variable.
This lays the groundwork for creating the application credential and clouds.yaml used by the CitC instance during terraform apply, removing the need to manually generate an application credential.
This PR also includes the following additional changes:
Allow specification of additional ssh/scp options (e.g. to configure jump host) using ssh_extra_flags Terraform variable (while temporary solution for clouds.yaml injecting into mgmt is in place)
Adds example terraform.tfvars and clouds.yaml files
This lays some groundwork for the changes suggested in issue #80.
Allow OpenStack API authentication information used by Terraform OpenStack provider to be different to OpenStack API application credential used by deployed CitC instance.
The application credential to be used by the deployed CitC is provided in a
clouds.yamlfile specified using theclouds_yamlTerraform variable. OpenStack API authentication for Terraform OpenStack provider can be separate to this, e.g. using a user/systemclouds.yamland cloud specified by environment variable.This lays the groundwork for creating the application credential and
clouds.yamlused by the CitC instance duringterraform apply, removing the need to manually generate an application credential.This PR also includes the following additional changes:
ssh/scpoptions (e.g. to configure jump host) usingssh_extra_flagsTerraform variable (while temporary solution forclouds.yamlinjecting into mgmt is in place)terraform.tfvarsandclouds.yamlfilesThis lays some groundwork for the changes suggested in issue #80.