Resolves the issue of the user not able to add pipelines to the kabanero custom resource file #13
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.
The user was not able to add pipelines to their custom resource upon using the
run.sh
file.What caused this issue was that the script was not counting the # of pipelines that currently exist in the
kabanero.yaml
file.This pull request resolves that issue by first counting the # of pipelines that exist in the stack key, and incrementing by 1 to add the new pipeline at the bottom.
Given the default kabanero pipelines i.e
where the user wants to add a new pipeline
The pull request now gives the following results in