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

Example Request: Chef Infra Server Cutover #55

Open
1 of 4 tasks
danielcbright opened this issue Oct 21, 2020 · 2 comments
Open
1 of 4 tasks

Example Request: Chef Infra Server Cutover #55

danielcbright opened this issue Oct 21, 2020 · 2 comments

Comments

@danielcbright
Copy link
Contributor

Example Request

  • Chef Automate
    • Includes Chef Server, Client, Backend, ChefDK and Supermarket
  • Chef Workstation
    • Includes Chef Workstation only
  • Habitat
    • Includes Habitat, Habitat Builder (on-prem and SaaS)
  • InSpec
    • Includes InSpec, Ad-hoc Automate jobs, Audit Cookbook

Problem Statement

What is the problem you're trying to solve that this example will help with?
For example, if you are trying to setup SAML for Automate using a third party
SSO provider, the problem you are trying to solve is "how to configure
Automate to use my third-party SSO provider for an externally managed IdP". Be
specific with the problem details as well, in the previous example, you would
want to make sure to name the SSO provider you need an example for, along with
details of versions, and anything else you can provide.

External References

  • Provide a bullet list of any links to external references that could help the
    person working on the problem.

Additional Notes

Provide anything else that can help the person working the problem.

@mattray
Copy link
Contributor

mattray commented Oct 22, 2020

Here's the recipe I used when I migrated from Hosted Chef to my local instance.
https://github.com/mattray/mattray-cookbook/blob/main/recipes/migrate.rb

@bd-br
Copy link

bd-br commented Oct 22, 2020

We are looking to migrate Chef Automate and Chef Server from on-prem to AWS. During this process we need to change the URL. We want to preserve all the settings, cookbooks, keys, instances, etc. on the new server. We'll also need to update the Chef clients with the new URL so that they check-in to the new server. We're not able to use DNS to do this.

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

No branches or pull requests

3 participants