Skip to content

Add CA choice template to multinode.sh #93

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

seunghun1ee
Copy link
Member

This change allows users to choose OpenBao or Hashicorp Vault as the certificate authority.

Copy link

@MaxBed4d MaxBed4d left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd prefer it if we kept this as a regular file rather than a template. It makes it easier to use & debug. Is there another way we could do this?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can have two separate multinode.sh. One for openbao and another for vault. Then conditionally copy only one of them to control host?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From discussions in other channels, we've agreed the best solution would be to unify the playbooks in SKC and make one generic set. For example, we replace openbao-unseal-overcloud.yml and vault-unseal-overcloud.yml with secret-store-unseal-overcloud.yml. We could then have a single variable in SKC to switch between the two types

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.

3 participants