Probably better to re-post here: :slightly_smiling...
# gitlab
s
Thinking about the possible resource types a bit more, a
Pipeline
with
ParentPipeline
and
ChildPipeline
references (perhaps similar to the Pulumi dependent stacks concepts) could also come in very helpful(?), with artifacts as input/output variables? On
pulumi up
, perhaps the GitLab-CI/CD pipeline could be run in full, via https://github.com/firecow/gitlab-ci-local (for local development), or remotely triggered if already committed(?) Just pipe-dreaming out loud here (yaml debugging really sucks). I'll try https://github.com/jkcfg/jk in the meantime 🙂, thanks for the recommendation! cc: @freezing-van-87649 @billowy-army-68599
👍 1
p
should it not be the other way around? you still need to have a yml file for GitLab to trigger the pipeline
here is my attempt (it works) to replace the deployment part
I want to try building the image there as well