Hi, I am trying to add a pulumi plugin (for scala support) in my Stack custom resource for the operator. I found this issue/comment which suggests adding an init container to achieve this. (I assume Stack.spec.workspaceTemplate.spec.podTemplate.spec) So far I've come across two issues with this approach, but I am just trying to get this to work relatively quickly so I may have missing something. 1. The documentation mentions that containers "cannot be updated". The reality seems to be that a container must be specified, otherwise the stack spec is invalid. See:

The Stack "git" is invalid: spec.workspaceTemplate.spec.podTemplate.spec.containers: Required value

. Specifying a dummy container works, and is added to the spec, although this should not be possible according to the docs. 2. It seems that when the spec is merged, all entires that are merged put the elements of the patch spec first. This is a problem, because the initContainer for adding a plugin must run after the two default initContainers "bootstrap" and "fetch". This is the probably very hacky spec I am trying:

workspaceTemplate:
    spec:
      podTemplate:
        spec:
          initContainers:
            - name: install-scala-cli-and-plugin
              image: curlimages/curl:latest
              command:
                - "/bin/sh"
                - "-c"
                - |
                  cd /share/workspace
                  curl -sSLf <https://scala-cli.virtuslab.org/get> | sh
                  pulumi plugin install language scala 0.3.2 --server <github://api.github.com/VirtusLab/besom>
          containers:
            - name: "dummy"
              image: busybox:latest

can you confirm you’re using the latest beta3 release of operator v2? iirc it should be treating this as a merge patch so i’m surprised it’s complaining about containers being required, but there could be a bug here.

Hi, yes, I am using the latest release. Also tried building the latest master branch and publishing the custom image