Design: Deployment build-pipeline-resource about pipeline HOT 4 CLOSED

I like it! I think this should be generic enough that we could define different types of deployers, e.g. kubectl as well as helm

from pipeline.

In my view a deployment output resource would be the output of a deployment task, so it would contain the metadata which resulted from the deployment, e.g. the release name and version in case of helm and perhaps a cluster resource. This could basically provide a kind of standard interface to tasks / pipelines who wanted to access the deployed "app" and that could work regardless of the deployment technology used in the deployment step.

However I don't think the deployment output resource should take care of the deployment itself, there should be a deployment task. Similar to how the image output resource does not take care of building and pushing an image, it will only receive the metadata of the built image from a kaniko task or some other build task.

from pipeline.

Don't think this is as relevant anymore given that PipelineResources are not in beta? @sbwsg can we close this?

from pipeline.

Yeah this doesn't look like it's hugely relevant anymore in the face of all the changes that have gone on around resources. If someone does want to revisit this specific idea then they can always reopen.

from pipeline.