Hello,
This partly determines on personal preference, and what kind of data it is. For things that need to be configured for each environment. Even if that is generally the same for each environment I recommend using a Wedge Address Configuration(https://docs.q2developer.com/docs/tutorials/online_banking/configuration.html). This will be stored in the database and easy to configure for each environment. If you have a setting that needs to only be on for a particular environment. Say always mock a request for the dev environment that is where you can use the DEPLOY_ENV flag(https://docs.q2developer.com/docs/guides/configuration.html#deploy-env).
If the values that are being stored needs to be secret like a private key or api key, I recommend using vault(https://docs.q2developer.com/docs/guides/performance_and_security/vault.html).
Hope this helps,
Trey Teter
This is very helpful, thank you.
— Eddie Suey 2 years agoWhat is the best way to manage wedge and vault configuration across the environments? Is this done outside of the extension via q2 commands? Or, in the deployment process? For example, let’s say we were storing a setting in the wedge that needed to be different for prod. How would we go about doing this?
Also, same scenario but for the vault (it looks like we may need to utilize both).
It looks like we can manage the configuration per environment via self-service.
— Eddie Suey 2 years agohttps://docs.q2developer.com/docs/guides/processes/configuration_editor.html