bcdevops / openshift-developer-tools

Tools for managing OpenShift projects.

OpenShift Project Tools

Welcome to the OpenShift project tools repository!

Here you will find tools to help you manage, automate, and maintain your OpenShift projects and pipelines.

The resources found in this repository will (should) be in a constant state of evolution as the community as a whole contributes their experiences using the existing tools and breaks new ground solving issues.

For this to happen we need your support. Please contribute! Whether that be with your experiences or with the code you used to solve a particular issue.

To contribute directly, please fork the repo and submit pull requests.

Thank-you and enjoy.

Sections

Jenkins

Jenkins pipeline related tools, utilities, and examples.

bin

A set of scripts for managing and maintaining OpenShift projects and configurations.

Refer to the OpenShift Scripts for details on how to use the scripts.

openshift-developer-tools's Issues

Always load default profile parameters BEFORE profile-specific parameters

When deploying configurations for a profile (e.g.: settings.myprofile.sh the developer scripts ignore the default parameter files and expect profile specific (e.g.: *.myprofile.param) files to be available.
It would be nice to have the scripts always load default profile parameters - if available - before the profile-specific ones: this would allow an additional level of configuration, and would facilitate deploying components that are shared and have the same configuration across profiles.

Desired behaviour:

• look up parameter files for default profile and load them, if available
• look up profile-specific parameter files and load them, if available, overriding/replacing the values previously set by the default profile

Parameter file generation should support values with white-space

This issue can be reproduced by cloning the repo https://github.com/bcgov/gcpe-NRMS-api and running genParams.sh from within the top level ./openshift directory.

How to reproduce:

1. Create a build (or deploy) template where a parameter that has a value with spaces in it;
   e.g. NAME: "Value1 Value2 Value3"
2. Run genParams.sh from within your top level ./openshift directory
3. Check the generated parameter file. Note that the generated value is:
   NAME=Value3

Expected Behaviour:

NAME=Value1 Value2 Value3