Allow OpenStack API authentication config for Terraform and deployed CitC to differ #79
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 theclouds_yaml
Terraform variable. OpenStack API authentication for Terraform OpenStack provider can be separate to this, e.g. using a user/systemclouds.yaml
and cloud specified by environment variable.This lays the groundwork for creating the application credential and
clouds.yaml
used by the CitC instance duringterraform apply
, removing the need to manually generate an application credential.This PR also includes the following additional changes:
ssh
/scp
options (e.g. to configure jump host) usingssh_extra_flags
Terraform variable (while temporary solution forclouds.yaml
injecting into mgmt is in place)terraform.tfvars
andclouds.yaml
filesThis lays some groundwork for the changes suggested in issue #80.