Right now, the only way how to give additional settings to the pipeline is through the additional-env parameter. The proposition is to create a way to provide some settings (only dns and auth0 keys right now) as a recurring parameters for every pipeline run. Secret/ConfigMap with these parameters can be created in the namespace with the pipeline and mounted during pipeline runs
Right now, the only way how to give additional settings to the pipeline is through the
additional-env
parameter. The proposition is to create a way to provide some settings (only dns and auth0 keys right now) as a recurring parameters for every pipeline run. Secret/ConfigMap with these parameters can be created in the namespace with the pipeline and mounted during pipeline runs