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

Plugins #283

Closed
mendrik opened this issue Mar 1, 2019 · 4 comments · Fixed by A-312/node-blueconfig#1
Closed

Plugins #283

mendrik opened this issue Mar 1, 2019 · 4 comments · Fixed by A-312/node-blueconfig#1

Comments

@mendrik
Copy link

mendrik commented Mar 1, 2019

would be great if one could add custom plugins where to fetch the variables from.
there is a built-in 'env' property, but it would be great if one could fetch something from somewhere else, like AWS secrets manager.

I would leave it up to the user to implement their own providers, but right now there is only the hardcoded env functionality.

@ebickle
Copy link

ebickle commented Jun 11, 2019

Agree as well - not necessarily broad plugin support, but some sort of "provider" infrastructure. I came here looking for ways to directly integrate S3 configuration management and AWS secrets manager, but it appears all we get is the "out of the box" functionality.

The hardcoded precedence order could be replaced with a default set of providers in a stack.

@madarche
Copy link
Collaborator

Good ideas. You are welcome to propose PR.

@brettneese
Copy link
Contributor

brettneese commented Aug 15, 2019

I had a PR for this (#273), but what I just realized is that you can leverage the convict.load() method for this by passing in a function that returns an object. I already have an SSM provider that works with my fork (https://github.com/HBKEngineering/convict-provider-awsSsm), but I'm working on modifying it to support native convict.

You can add custom keys to your config (ie "providerPath: '/blah'" ) to do this, convict won't mind.

@A-312
Copy link
Contributor

A-312 commented Dec 7, 2019

Similar/Duplicate : #313

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 a pull request may close this issue.

5 participants