No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

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 :slightly_smiling_face:, thanks for the recommendation!

cc: <@U02A2BPBBGF> <@UCWG26BH7>

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

<https://zimarev.com/blog/devops/2022-02-16-gitlab-pulumi-dotnet/>

I want to try building the image there as well