[RFR] Add 'env' field to IQE CJI spec #855
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds an
env
field to the IQE CJI spec which allows anyone invoking a CJI to set a list ofEnvVar
s that will be passed on to the IQE Job pod.We will mark most of the fields that Clowder has been parsing and setting on the Job's pod here as deprecated and instead we'll begin to have the bonfire IQE CJI template define the structure of these env vars itself. We will also need to make sure anyone invoking a CJI without using bonfire updates their resource config before we remove the deprecated fields.
At the moment while both the "old fields" and the "new"
env
field exist, the behavior will be:env
to the arrayenv
conflict with those already set in step 1, we will override whatever is currently set in the array and use the value defined in theenv
block.