Trying to catch helm release not found errors

[dalefrancum]

What

• Add an extra check to see if helm will fail trying to query a release
• It exits with a 0 so there's not a failure
• This also removes the "Skipping"; optional, we can leave that in if desired

Why

• We had a project failing with "release not found" errors running helm history. The idea here is to catch a helm failure and then just skip.
• I don't think this should be permanent, just seeing if we can identify what the problems are without impacting deployments.

Testing

Test with an existing release.

❯ ./check-if-already-updated.bash restaurant-etl-dim-tax-staging restaurant-etl
***********************************
RELEASE_NAMESPACE: restaurant-etl
RELEASE_NAME: restaurant-etl-dim-tax-staging
DEPLOYMENT: restaurant-etl-dim-tax
***********************************
Needs updating.

❯ ./spoton-monochart-labels-updater.bash restaurant-etl-dim-tax-staging restaurant-etl
👷 Confirming that deployment restaurant-etl-dim-tax exists before continuing...
***********************************
RELEASE_NAMESPACE: restaurant-etl
RELEASE_NAME: restaurant-etl-dim-tax-staging
DEPLOYMENT: restaurant-etl-dim-tax
SERVICE: restaurant-etl-dim-tax
TEMP_DEPLOYMENT: restaurant-etl-dim-tax-temp
***********************************

⚠️  This was a dry run. No changes were made.

Test with a pretend release.

❯ ./check-if-already-updated.bash restaurant-etl-dim-tax-staging-foooo restaurant-etl
Error: release: not found

⚠️  Could not get status for restaurant-etl-dim-tax-staging-foooo in namespace restaurant-etl. Skipping.

❯ ./spoton-monochart-labels-updater.bash restaurant-etl-dim-tax-staging-foooo restaurant-etl
Error: release: not found

⚠️  Could not get status for restaurant-etl-dim-tax-staging-foooo in namespace restaurant-etl. Skipping.