Arjun Raman

Hey @TatanParker, to use the 'service' feature on GitHub Actions, the username and password must be the username and password must be Docker credentials. You can find how to access...

@kurtislamb so the issue is that a key (e.g. ecr_password) under the 'outputs' key doesn't populate if the value given to it is a secret, which the password outputted by...

@kurtislamb under one of your workflow runs, you should see a annotation with a warning that says something like "Skip output 'ecr_password' since it may contain secret."

@kurtislamb @kylebyerly-hp the change removing the 'secret' status of the Docker password was just released.

@anuj-scanova, I was able to replicate your issue. It seems like the 'RELEASE_TAG' environment variable is null. So it's not erroring on the push, but rather on the second tag....

@mdouglass @TzlilSwimmer123 @joekhoobyar @CaBazaga @renperez-cpi @netanelrabinowitz apologize for the delay, should be released now!

Could I see you workflow yml with all sensitive info redacted?

Ah I see. The way GitHub actions marks secrets in logs is by checking every substring in the logs to see if they match any of the secret values. In...

Not sure, I haven't tried to do so. I gave a possible solution in #464. Other related discussions can be found in #495 and #496. Here's a doc from GitHub...

Could you paste the exact error from your logs here, covering any sensitive information?