Introduce component "objects" ( aka list of Kube objects )

[sbose78]

As a stack/devfile author, I wish to convey outer-loop deployment guidance in the form of a list of parameterized kubernetes objects.

The format draws inspiration from Templates https://github.com/sbose78/nodejs-rest-http-crud/blob/master/.openshiftio/application.yaml#L38

---

 components:   
   -  id: deploy-node-app
      parameters:
         - name: ${image}
           value: quay.io/quarkus-quickstarts/getting-started-knative ## Default
       objects:
         - apiVersion: serving.knative.dev/v1alpha1
            kind: Service
            metadata:
              name: greeter
            spec:
              template:
                spec:
                  containers:
                    - image: ${image}
                      livenessProbe:
                      httpGet:
                        path: /health/live
                      readinessProbe:
                      httpGet:
                        path: /health/ready

If the objects component is associated with a dockerfile component (image build guidance) in a composite command, #51 , che/odo must associate the built image from the 'build' guidance using the image parameter.

- composite:
      id: build-and-deploy
      label: Build image and deploy nodejs app
      commands:
      - build-node-app
      - deploy-node-app
      parallel: false
      group: 
          kind: deploy

[EnriqueL8]

Would it be simpler for a user to have the ability to specify a path or a link to a deployment manifest containing these objects? The tool consuming this would then apply the templating on that file.

[l0rd]

@EnriqueL8 that is already supported using a component of type kubernetes.

[github-actions]

This issue is stale because it has been open for 90 days with no activity. Remove stale label or comment or this will be closed in 60 days.