Inconsistency in UI between Soruces -> Create Source and Pipelines -> Create Source
Minor nitpick here, but it initially lead me down the path of thinking that one couldn't use git as a source for Create Image in Pipelines. Please see attached images :)
Attachments
Looks like the image attachments don't work xD
Images has the following list
- Docker Hub
- Docker Registry
- Docker File - Git Repo
- Docker File - Tarball
- OCI Registry
Pipelines has the following:
- Docker Hub
- Docker Registry
- Docker File
- OCI Registry
After selecting Docker File, then you can pick between git and tarball.
Also it appears that you can't select the builder in the Create Image Source pipeline stage, but I might just be blind...
Hey Jeremy, that pipeline step is actually going to be deprecated. Can you tell me more about why you'd like to use it in the pipeline and I can suggest so way to achieve this outside of the Create Image Source pipeline step.
I have a specific environment set up, and I want to be able to deploy any branch to a container in that environment -- my assumption is that I have to create a source and then build the image, but perhaps I can just build the image without creating a source?
As Chris mentioned, we'll likely be getting rid of this step. It doesn't really make sense in pipelines given that every pipeline run would yield a new image source. It'd be better to handle this with stacks as they provide maximum flexibility without resulting in a bunch of one-off image sources that eventually would need cleaned up.
Quick side note Jeremy, we pushed an update to resolve the thread image issue you encountered. Thanks for bringing that to our attention!