Kevin Bennett

> I think meteor-up is better than deploymeteor, so I don't put in much effort on this anymore, but I'll accept a PR if you figure out a solution. It...

I think it could be a good idea. Just need to be careful that there are stacks involved as well. Values will be constructed by swarm-sync for a deployment/update so...

Latest solution is SS calls SP->inspectPack() to get the latest commit but SS manages the state of what is currently deployed. I'm not sure if we can move this responsibility...

I agree in theory that version might be better than commit hash. But I have reservations: - I really don't like keeping the version in package.json or another file. It's...

Seems like Helm uses version number, and version is always incremented for a commit, e.g. https://github.com/helm/charts/commit/734a8761e58793e09c15467af87fa535bde696f9 I wonder if it's possible to automate this or have a safeguard, like a...

Related issue in Flux with discussion: https://github.com/weaveworks/flux/issues/738

Definitely need this feature! A few questions: - Do I need to specify all values again when upgrading? Can I reuse some values / all values from initial deployment? -...

How do we handle values: - What if pack requires additional /different value on upgrade? (better error messages will help) - Update / add / delete a specific value when...

Similar issue in Helm: https://github.com/helm/helm/issues/1950

Added PR #20