Skip to content

Product gap in DR/HA use around keys/certs. #278

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.

Sign up for GitHub

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

Jump to bottom
Closed
cummingscody opened this issue Aug 8, 2022 · 0 comments · Fixed by #281
Closed

Product gap in DR/HA use around keys/certs. #278

cummingscody opened this issue Aug 8, 2022 · 0 comments · Fixed by #281
Labels
feature jira

Comments

@cummingscody
Copy link

cummingscody commented Aug 8, 2022 •
edited
Loading

Use Case

Product gap in DR/HA impacting customers.

Describe the Solution You Would Like

The following files need copied over when configuring a replica or reusing a failed primary, as well as an update to documentation around this:

  • /opt/puppetlabs/server/data/console-services/certs/ad_ca_chain.pem
  • /etc/puppetlabs/orchestration-services/conf.d/secrets/keys.json
  • /etc/puppetlabs/orchestration-services/conf.d/secrets/orchestrator-encryption-keys.json
  • /etc/puppetlabs/console-services/conf.d/secrets/keys.json

Describe Alternatives You've Considered

The alternative is to introduce manual workarounds into an automated process.

Additional Context

Internal ZD 47932
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature jira
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Re-use sync_global_hiera plan ody/puppetlabs-peadm
2 participants
@timidri @cummingscody