Pulling APP_NAME and NAMESPACE_PREFIX parameters from env of github actions workflows code, replacing them with github repo level variable.
CHEFS contributors who need to run their own OpenShift projects cannot use github actions code to deploy application components to their own OpenShift projects since the OpenShift prefix for project names is hardcoded in env params of workflow definitions. Same goes to APP_NAME that needs to be overridden to unique value sisnc eit is used when gererating domain where application will be exposed (OpenShift Route object).
The changes allow to have new values supplied into Github Actions from github repo level (upstream or fork).
Types of changes
New feature (non-breaking change which adds functionality)
Description
Pulling APP_NAME and NAMESPACE_PREFIX parameters from env of github actions workflows code, replacing them with github repo level variable.
CHEFS contributors who need to run their own OpenShift projects cannot use github actions code to deploy application components to their own OpenShift projects since the OpenShift prefix for project names is hardcoded in env params of workflow definitions. Same goes to APP_NAME that needs to be overridden to unique value sisnc eit is used when gererating domain where application will be exposed (OpenShift Route object). The changes allow to have new values supplied into Github Actions from github repo level (upstream or fork).
Types of changes
New feature (non-breaking change which adds functionality)
Checklist
Further comments
This solution have been already discussed with CoCo team.