Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow OpenStack API authentication config for Terraform and deployed CitC to differ #79

Open
wants to merge 5 commits into
base: openstack
Choose a base branch
from

Conversation

jcwomack
Copy link

@jcwomack jcwomack commented Apr 12, 2024

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.

* clouds_yaml: clouds.yaml used by CitC instance for OS API auth
* ssh_extra_flags: specify additional flags for scp command used in temporary solution to inject clouds.yaml to mgmt in compute.tf
These options can instead be set using environment variables
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant