Skip to content
This repository has been archived by the owner on Aug 2, 2023. It is now read-only.

Add a field for default pipelines in a Stack CR instance #763

Open
kaczyns opened this issue Jun 11, 2020 · 0 comments
Open

Add a field for default pipelines in a Stack CR instance #763

kaczyns opened this issue Jun 11, 2020 · 0 comments

Comments

@kaczyns
Copy link
Member

kaczyns commented Jun 11, 2020

This is a child issue of #647.
There is a desire to have a default set of pipelines for a Stack CR. These would be applied to all versions of the stack defined in the CR. A new set of pipeline information (field called pipelines) should be created at the top level of the Stack CR spec section.

The stack controller should use these default stack pipelines if the specific stack version does not contain any. Considered holistically with #762, we now have three places we could be pulling pipelines from when the stack controller is running in Odo mode. Here is the list, in priority order from highest priority to lowest:

  1. From the spec.versions[x].pipelines in the Stack CR instance
  2. From spec.pipelines in the Stack CR instance
  3. From the Kabanero CR instance

Note that when the stack controller is running in Appsody mode, there is no need to use the spec.pipelines in the Stack CR instance, as the kabanero controller is not going to set that field when processing an appsody stack hub. However if it makes the implementation easier, the stack controller could use 1) or 2) in both modes. It should not use 3) in Appsody mode.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant