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

docs: Add another multi-tenancy secret management method for AVP #501

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

Conversation

Orabig
Copy link

@Orabig Orabig commented Apr 25, 2023

Description

Documentation about multitenancy secret management, as sugggested in #491

Checklist

Please make sure that your PR fulfills the following requirements:

  • Reviewed the guidelines for contributing to this repository
  • The commit message follows the Conventional Commits Guidelines.
  • [N/A] Tests for the changes have been updated
  • [N/A] Are you adding dependencies? If so, please run go mod tidy -compat=1.17 to ensure only the minimum is pulled in.
  • Docs have been added / updated
  • Optional. My organization is added to USERS.md.

Type of Change

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • New tests
  • Build/CI related changes
  • Documentation content changes
  • Other (please describe)

@@ -109,6 +109,10 @@ A common use-case is to be able to use _multiple_ secret backends for generating

For this to work, AVP must be configured to use specific credentials for generating the manifests of an app. This can be done in one of 2 ways:
Copy link

Choose a reason for hiding this comment

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

It's one of three ways now :-)

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