feat: add netlify-plugin-use-env-in-runtime

[bentocodeing]

Description:

This plugin allows you to transfer environment variables in the runtime of your application from those declared in your netlify.toml file and which are only executed at build time.

You can even override variables defined in the Netlify UI!

---

Thanks for contributing the Netlify plugins directory!

Are you adding a plugin or updating one?

• Adding a plugin
• Updating a plugin

Have you completed the following?

• Read and followed the plugin author guidelines.
• Included all required fields in your entry.
• Tested the plugin locally and on Netlify, using the plugin version stated in your entry.

Test plan
Please add a link to a successful public deploy log using the stated version of the plugin. Include any other context reviewers might need for testing.

For test plan, see: https://app.netlify.com/sites/use-env-in-runtime-plugin-demo/deploys/6106f295e858e60008be2c41

[netlify-bot]

Added Packages

• https://registry.npmjs.org/netlify-plugin-use-env-in-runtime/-/netlify-plugin-use-env-in-runtime-1.2.1.tgz

[eduardoboucas]

Hi @ARKHN3B! Thanks for submitting your plugin.

As per our Plugin Author Guidelines, plugins must provide a zero-config default if they are to be installable via the UI. This includes not relying on required inputs, which your plugin seems to do.

Can you change it so that you're able to provide a zero-config default?

[ehmicky]

Thanks a lot for this plugin @ARKHN3B!

This is a great idea. One popular Build plugin netlify-plugin-contextual-env is quite similar. The only difference is that the prefix is always "context or branch" instead of being user-defined.

What are your thoughts on adding that feature to this existing plugin instead? For example, you could add a prefixes input and make it default to [context, branch].

[bentocodeing]

Thanks a lot for this plugin @ARKHN3B!

This is a great idea. One popular Build plugin netlify-plugin-contextual-env is quite similar. The only difference is that the prefix is always "context or branch" instead of being user-defined.

What are your thoughts on adding that feature to this existing plugin instead? For example, you could add a prefixes input and make it default to [context, branch].

Thank you for the suggestion @ehmicky!

I think this changes the philosophy of this plugin a bit. But I'm 💯 up for collaborating on this project and adding this logic on it.

I will work on it and submit a PR soon 🙂

[ehmicky]

Thanks @ARKHN3B!

[bentocodeing]

Hi @ARKHN3B! Thanks for submitting your plugin.

As per our Plugin Author Guidelines, plugins must provide a zero-config default if they are to be installable via the UI. This includes not relying on required inputs, which your plugin seems to do.

Can you change it so that you're able to provide a zero-config default?

Thank you for your response @eduardoboucas!

I've been working on it and I think my plugin fits Netlify's requirements now 🙂

[ehmicky]

Thanks for your patience @ARKHN3B!
I have found a few minor issues, which I reported on your repository. Please let me know what you think!

[bentocodeing]

Thanks for your patience @ARKHN3B!
I have found a few minor issues, which I reported on your repository. Please let me know what you think!

Thanks to you @ehmicky ! 💯

Good comments, thank you for the time you used to review my code. It's always good to have an external feedback. 🙂

I've had time to implement your feedback, it should be fine now.

[ehmicky]

Thanks @ARKHN3B! 🎉