Document how to supply multi-value input for access_token_scopes #380
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Because GitHub Actions has a limitation that YAML arrays cannot be used as inputs (which is a wild choice on their part IMO), different actions each have their own strategy for accepting multi-value inputs. There doesn't seem to be a standard approach, for instance
get-secretmanager-secrets
parsessecrets
as a multi-line input with each secret on a new line, whereas this repo parses list inputs as a single-line comma-separated list.I found it confusing that the documentation just says "List" and you have to dig into the code to find the
parseCSV
to tell how a multi-value input should be provided for this input.