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

adding GCS Backup Documentation #4106

Merged
merged 9 commits into from
Aug 10, 2020
Merged

adding GCS Backup Documentation #4106

merged 9 commits into from
Aug 10, 2020

Conversation

danielcbright
Copy link
Contributor

Signed-off-by: Daniel Bright danielcbright@gmail.com

🔩 Description: What code changed, and why?

This is a PR to add documentation for the GCS Backup support that was added via PR #3609 thanks to the great work by @mskdenigma and @jaym .

⛓️ Related Resources

backup and external backup configurations and related documentation

👍 Definition of Done

Documentation is signed off by the appropriate teams

👟 How to Build and Test the Change

Testing is already done for the functionality of the GCS backups, this is just documentation

✅ Checklist

📷 Screenshots, if applicable

Signed-off-by: Daniel Bright <danielcbright@gmail.com>
@danielcbright danielcbright requested a review from a team as a code owner July 21, 2020 16:04
@mjingle mjingle self-assigned this Jul 21, 2020
@mjingle mjingle added the documentation Anything related to the Automate docs. label Jul 21, 2020
@mskdenigma
Copy link
Contributor

LGTM!

@susanev susanev added the community issues submitted by community folks label Aug 5, 2020
# protocol = "https"
```

##### Backup to GCS
Copy link
Contributor

Choose a reason for hiding this comment

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

@danielcbright Is this section the equivalent of "Backup Externally-Deployed Elasticsearch to GCS"? or is this not for externally-deployed Elasticsearch?

Copy link
Contributor Author

@danielcbright danielcbright Aug 5, 2020

Choose a reason for hiding this comment

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

also ok with this, oops, wrong comment on wrong part!

Yes, looking back at it now, it doesn't really flow very well, but yes, this is specific to externally deployed ES

Mary Jinglewski added 2 commits August 7, 2020 10:49
Signed-off-by: Mary Jinglewski <mjinglewski@chef.io>
Signed-off-by: Mary Jinglewski <mjinglewski@chef.io>
@susanev
Copy link
Contributor

susanev commented Aug 7, 2020

@danielcbright can you rebase this on master?

@danielcbright
Copy link
Contributor Author

Looks like the build is finding "possible credentials"


Checking for possible credentials in the source code
--
  | components/automate-chef-io/content/docs/backup.md:  "private_key": "-----BEGIN PRIVATE KEY-----\nXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX\n-----END PRIVATE KEY-----\n",
  | Possible credentials found. See above output for details.
  | exit status 1

Is there any way around this?

Signed-off-by: Daniel Bright <danielcbright@gmail.com>
@susanev
Copy link
Contributor

susanev commented Aug 10, 2020

@danielcbright yah you can add an exception for it, i think you and mary decided to go another way but let me know if you need to know how and ill ask in a2-team

Signed-off-by: Daniel Bright <danielcbright@gmail.com>
@mjingle mjingle self-requested a review August 10, 2020 18:07
@susanev susanev merged commit 28aa0d4 into chef:master Aug 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community issues submitted by community folks documentation Anything related to the Automate docs.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants