URLSearchParams to split process.env variables

[dbauszus-glx]

Where multiple process.env variables are required to support a single module it would be advantageous to provide a single environment variable which can split with URLSearchParams.

This could be applied for SAML2, Mailer [TRANSPORT], dbs, and possibly more.

Object.fromEntries(new URLSearchParams(process.env.DBS).entries())

[dbauszus-glx]

Having a config/env module for the process.env variables may help with transofrmations, defaults, and documentation as well.

https://www.youtube.com/watch?v=kgiwKbKcSyk

[RobAndrewHurst]

Having a config/env module for the process.env variables may help with transofrmations, defaults, and documentation as well.

https://www.youtube.com/watch?v=kgiwKbKcSyk

This kind of thing is already built into dotenv.

[RobAndrewHurst]

Where multiple process.env variables are required to support a single module it would be advantageous to provide a single environment variable which can split with URLSearchParams.

This could be applied for SAML2, Mailer [TRANSPORT], dbs, and possibly more.

Object.fromEntries(new URLSearchParams(process.env.DBS).entries())

Also this needs more clarification. Are we talking about (as an example) a single string that has all the different possible DB_* entries?

[RobAndrewHurst]

https://github.com/dotenvx/dotenvx

I think the route of a single entry for module doesn't quite make sense to be as it will quite hard to read when configuring/debugging.

I think we should possibly make use of a package like the new dotenvx which we can use to combine multiple .env files which we can use to split up different module .env variables.

As for getting all the different variables that we would need for a module we should just be able to provide a prefix and get them from the process.

const getEnvsByPrefix = (prefix) => {
  return Object.keys(process.env)
    .filter(key => key.startsWith(prefix))
    .reduce((obj, key) => ({
      ...obj,
      [key]: process.env[key]
    }), {});
};

Something like this would be ideal where we could provide DB_ to the function and get all the keys returned.

[cityremade]

more complex functions on variables can be implemented in the configuration module.
That way we can have all in one place.
For now I've only used iteration on process.env values but surely there are lost of possibilities to expand it.