You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a bug in helm (2 for sure, unclear when using version 3) that can allow a release to have multiple revisions marked as DEPLOYED. Because of this all of those revisions get listed in pluto output. We should only care about the most recent one.
Bonus: should we also alert the user they are hitting this bug? It is not a feature of helm to have more than one DEPLOYED release at at ime.
The text was updated successfully, but these errors were encountered:
… name output for helm (#67) (#69)
* should not show duplicate deployed releases and adds release name to output for helm
* fixing e2e tests
* another try at fixing e2e testing expected output format
* adding back spacing at end to see if e2e runs successfully
* removing debug log line
* removing extra space from e2e tests
* Update pkg/helm/helm.go
Co-Authored-By: Andrew Suderman <andrew@sudermanjr.com>
* deleting hostpath-provisioner helm chart which is throwing off spacing in e2e
* Trying a new codecov yaml
* break out marshal functionality a bit more
Co-authored-by: Andrew Suderman <andrew@sudermanjr.com>
There is a bug in helm (2 for sure, unclear when using version 3) that can allow a release to have multiple revisions marked as DEPLOYED. Because of this all of those revisions get listed in pluto output. We should only care about the most recent one.
Bonus: should we also alert the user they are hitting this bug? It is not a feature of helm to have more than one DEPLOYED release at at ime.
The text was updated successfully, but these errors were encountered: