-
Notifications
You must be signed in to change notification settings - Fork 121
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
ParameterOverrides with commas in them fail #47
Comments
|
I can confirm that this is an issue. It doesn't even honor quotes around the comma delimited list. Working on a fix. Will submit a pull request soon. |
Hi @damian-bisignano , were you able to find a solution? |
Argh, this is a killer, any movement toward a fix here? |
@matthewmrichter , multi-value key is supported by using the very intuitive syntax:
|
@dror-weiss This issue is talking about individual parameters that have commas within them:
There seems to be no syntax, very intuitive or not, to accomplish that |
@matthewmrichter As per:
Specifying multiple duplicate "ParameterKey" will concatenate them in one with comma separated ParameterValues. So:
Will be passed to Cloudformation as
Thank you @dror-weiss for noticing this. |
Confirming that the issue still exists. Specifying multiple duplicate keys is not necessarily feasible in all scenarios. I may not always know how many subnets I have in the action and that also limits me creating a generic action that can handle multiple subnets - could be 2/3/4. I can't get it to work w/o writing convoluted code in my action to generate the proper syntax and inject it into the call. Handling commas in the value field is really a missing feature here. |
This is still an issue. Situations where the parameter contains a comma but is not an array cannot be addressed by the "duplicate parameter" workaround. For example a parameter with the value of a cronjob string - is not passable at the moment if it has a comma in it. Has anyone discovered out a workaround? |
I've got a parameter that is a comma separated list. this doesn't work it instead splits on this value, expecting it to be another Key-Value pair
i've tried with all sorts of combinations of " and ' around the parameters and couldn't get it working.
the error i get is
Error: Invalid input for parameter key subnet-22222222". Need to specify either usePreviousValue as true or a value for the parameter
I imagine the update just needs to be update src/utils.ts line 52 to update to a regex that ignores if you have an escape character before the comma
Alternatively. update to use newline character for seperating. you won't have a newline character in your parameters from what i can think of in my use cases
The text was updated successfully, but these errors were encountered: