How are you supposed to manage multiple overlays with Ship?

[ianwalter]

For example, if I’m trying to use Ship to manage a Redis instance for dev and staging how would I do that? Would I just copy the ship overlay and rename it? Or am I supposed to keep them in separate directories (run ship init twice)?

[laverya]

Unfortunately, we don't have provisions for multiple ship targets yet. We do have a solution in our cloud environment, but that is to run ship with any common settings and changes, and then to run two additional ship instances that use the rendered yaml of the first as their base in order to apply staging or dev-specific changes. But of course that still means running ship more than once.

[laverya]

@ianwalter, expanding on this a little - if you're willing to forego total ship management of your process, it should be possible for you to run ship to setup your dev environment, move overlays/ship to overlays/dev, and then rerun (with ship update --headed or ship edit) to setup your staging overlays.

ship update would still work, though you would need to generate your dev yaml afterwards with kustomize overlays/dev.