AWS Secrets should be treated as GitHub Workflow secrets about invoke-aws-lambda HOT 5 CLOSED

@burz Thanks for all your help! version 3.3.1 has carries all the changes! and master as well of course.

from invoke-aws-lambda.

Thanks for your help with this @gagoar !

from invoke-aws-lambda.

Hey @burz. thanks for the issue. What I think we could do, is start using @main for this change, and leave master as just another branch. I should be using @main anyways. That would break nothing on legacy systems and every newcomer will get the main version.

thoughts?

from invoke-aws-lambda.

That seems reasonable to me! Unfortunately it seems like the secret treatment as part of reusable workflows may be a rather recent change since many many actions don't seem to differentiate in terms of their inputs.

from invoke-aws-lambda.

I realize that the change to ensure the secrets are masked doesn't, in the end, necessitate a switch of branches since the change is still backwards compatible, so I'll make a PR to the master branch.

Thanks again,
-burz

from invoke-aws-lambda.