-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Promote flag default doesn't agree with docs #361
Comments
Since upgrading the deployment action from v0 to v2, and stumbling into google-github-actions/deploy-appengine#361, new versions were not properly promoted. However, our promotion setting in the workflow was actually ignored the whole time due to a missing "echo". Closes shaka-project#6502
Since upgrading the deployment action from v0 to v2, and stumbling into google-github-actions/deploy-appengine#361, new versions were not properly promoted. However, our promotion setting in the workflow was actually ignored the whole time due to a missing "echo". Closes #6502
Since upgrading the deployment action from v0 to v2, and stumbling into google-github-actions/deploy-appengine#361, new versions were not properly promoted. However, our promotion setting in the workflow was actually ignored the whole time due to a missing "echo". Closes #6502
The default value in the |
Yes. I was passing a value that happened to be blank due to a dumb workflow bug. with:
promote: ${{ env.APPSPOT_PROMOTE }} That variable was meant to be "true" or "false", but it was left out of the environment entirely. It would appear that the default in action.yml was not used in this case. This didn't become obvious until I upgraded from v0 to v2, since v0 had the default implemented explicitly in TypeScript. |
This restores a v0 and v1 behavior wherein the empty string is considered "true" instead of "false". Fixes GH-361.
Right - if you pass in a value, it will use the empty string (whereas not providing a value uses the default). |
This restores a v0 and v1 behavior wherein the empty string is considered "true" instead of "false". Fixes GH-361.
Thanks! |
Since upgrading the deployment action from v0 to v2, and stumbling into google-github-actions/deploy-appengine#361, new versions were not properly promoted. However, our promotion setting in the workflow was actually ignored the whole time due to a missing "echo". Closes #6502
Since upgrading the deployment action from v0 to v2, and stumbling into google-github-actions/deploy-appengine#361, new versions were not properly promoted. However, our promotion setting in the workflow was actually ignored the whole time due to a missing "echo". Closes #6502
Since upgrading the deployment action from v0 to v2, and stumbling into google-github-actions/deploy-appengine#361, new versions were not properly promoted. However, our promotion setting in the workflow was actually ignored the whole time due to a missing "echo". Closes #6502
Since upgrading the deployment action from v0 to v2, and stumbling into google-github-actions/deploy-appengine#361, new versions were not properly promoted. However, our promotion setting in the workflow was actually ignored the whole time due to a missing "echo". Closes #6502
TL;DR
The promote flag is documented as defaulting to true, but actually defaults to false.
Expected behavior
In v0, it was defaulted to true with:
Observed behavior
In v2, there is no explicit default anywhere, so the parseBoolean default of
false
takes over.Action YAML
# N/A AFAICT
Log output
Additional information
If the docs are correct, I believe the fix could be as simple as changing:
to:
If the docs are wrong, then the obvious fix is to correct the docs.
The text was updated successfully, but these errors were encountered: