<release> has no deployed releases

[jkroepke]

Related: helm/helm#3597

When using helm upgrade --install, if the first release fails, Helm will respond with an error saying that it cannot upgrade from an unknown state.

The current workaround is to use helm upgrade --install --force but a handling like this is missing in helm diff.

helm diff upgrade dyn . --allow-unreleased -q 
"dyn" has no deployed releases
Error: "dyn" has no deployed releases
Error: plugin "diff" exited with error

It would be great if this plugin could be catch this error.

[keramblock]

Has same issue, when I tried to use this plugin in CI/CD =(

[mumoshu]

Yeah this is very frustrating! But my impression was that this should be handled outside of helm-diff.

For example, the latest version of helm added --atomic option to helm install and helm upgrade --install, which automatically removes the stale release that causes this issue. Even with the feature, do we still need this handled in helm-diff?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[jkroepke]

Poke Am 08.11.2019 um 06:03 schrieb stale[bot] <notifications@github.com>:  This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#108?email_source=notifications&email_token=AAL5AC7Z5SAUBIPG4NSGR2TQSTXINA5CNFSM4GBNKEMKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDOXVRQ#issuecomment-551385798>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAL5AC4FYE6DIHHA7SMZ7W3QSTXINANCNFSM4GBNKEMA> .

[mumoshu]

@jkroepke Hey! I'm curious - what helm-diff should do? I'd rather suggest you run helm upgrade --install --atomic whenever you install, so that you and helm-diff would never need to handle it.

[jkroepke]

Hey! I'm curious - what helm-diff should do?

If there is no deployed releases handle it like an install.

[mumoshu]

@jkroepke Thanks! Then you or your CI always run helm upgrade --install --force?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[jkroepke]

Thanks! Then you or your CI always run helm upgrade --install --force?

In dev environments and certain changes requires force flag.

But how is the question related to this issue?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.