drone-helm has a handful of settings that correspond to helm2 commands/flags that don't exist in helm3. If we see those env vars, it probably means they were left over during an upgrade from drone-helm. drone-helm3 should emit a warning that advises the plugin consumer to remove those config settings. We don't want a user to experience the frustration of "I've set this setting, why isn't it being applied??"
Deprecated env vars:
PURGE (for adding --purge to helm delete. helm3's delete command has no --purge flag)
RECREATE_PODS (for adding --recreate-pods to helm upgrade. helm3's upgrade command has no --recreate-pods flag)
TILLER_NS (Tiller setting)
UPGRADE (Tiller setting)
CANARY_IMAGE (Tiller setting)
CLIENT_ONLY (Tiller setting)
STABLE_REPO_URL (Tiller setting)
Remember to look for both the prefixed and non-prefixed forms (e.g. $PURGE and $PLUGIN_PURGE).
drone-helm has a handful of settings that correspond to helm2 commands/flags that don't exist in helm3. If we see those env vars, it probably means they were left over during an upgrade from drone-helm. drone-helm3 should emit a warning that advises the plugin consumer to remove those config settings. We don't want a user to experience the frustration of "I've set this setting, why isn't it being applied??"
Deprecated env vars:
PURGE(for adding--purgetohelm delete. helm3'sdeletecommand has no--purgeflag)RECREATE_PODS(for adding--recreate-podstohelm upgrade. helm3'supgradecommand has no--recreate-podsflag)TILLER_NS(Tiller setting)UPGRADE(Tiller setting)CANARY_IMAGE(Tiller setting)CLIENT_ONLY(Tiller setting)STABLE_REPO_URL(Tiller setting)Remember to look for both the prefixed and non-prefixed forms (e.g.
$PURGEand$PLUGIN_PURGE).