Skip to content
This repository has been archived by the owner on Jul 26, 2022. It is now read-only.

Enforcing naming conventions for AWS Secrets Manager (and HashiCorp Vault) entries #230

Merged
merged 4 commits into from
Dec 9, 2019

Conversation

muenchhausen
Copy link
Contributor

See issue #178.

This patch is tested. It runs smoothly on two clusters since more than 4 weeks.

@muenchhausen muenchhausen changed the title Enforcing naming conventions for AWS Secrets Manager entries Enforcing naming conventions for AWS Secrets Manager (and HashiCorp Vault) entries Nov 24, 2019
@muenchhausen
Copy link
Contributor Author

Documentation is missing for both useages

  1. AWS Secrets Manager
  2. HashiCorp Vault

I will add that, if this pull request is of interest.

config/environment.js Outdated Show resolved Hide resolved
lib/poller.js Show resolved Hide resolved
Copy link
Contributor

@silasbw silasbw left a comment

Choose a reason for hiding this comment

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

Thanks for this contribution 🥂

Do you have any examples of similar operations performed in native Kubernetes objects or well-known extensions? I'm curious how those approaches compare to this one.

We'll also need some updates to the docs explaining how to use this.

Copy link
Member

@Flydiverny Flydiverny left a comment

Choose a reason for hiding this comment

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

looks good to me

@Flydiverny Flydiverny merged commit c4fdea6 into external-secrets:master Dec 9, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants