-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Fn::Join no longer works with nested Fn:: methods #1076
Comments
For L2 instances, there is slightly different voodoo you have to do for a workaround. The cast return new Ssm.ParameterResource(this, 'MicrosoftAdDnsIpAddressesParam', {
name: this.domainSsmParameterPrefix + 'directory-dns',
type: 'StringList',
value: {
'Fn::Join': [
this.delimeter,
microsoftAdDnsIpAddresses.resolve()
]
} as unknown as string, |
Thanks for reporting, having a look |
Your current best workaround will be this: new Fn('Fn::Join', [', ', adResource.microsoftAdDnsIpAddresses]) Until we sort that issue. |
I'm going to close this, as your issue is a more specific case of another issue: lack of support for array tokens, and there is a workable workaround for it. Feel free to reopen if you disagree. |
Problem file: fn.ts
Problem method: FnJoin constructor
Last working version: 5bb7c93 (0.13)
Broke in version: 33c32a8 (current, 0.14.1)
Problem
FN::Join
no longer work when thelistOfValues
parameter contains another function, such asFn::GetAtt
.For example, this code attempts to output the array of IP addresses for an AD Resource:
Cause(?)
It looks like the latest changes to
FN::Join
are designed to unpack nested joins, but I don't see how this would work if the join contained a non-join function.There was a previous commit 5996442 that did something similar, but was rolled back for unrelated reasons. That commit seems to be doing a lot more to make sure there were only nested joins before unpacking them. Maybe that logic can be brought in?
Until then, I am handwriting
Fn::Join
json objects as a workaround.The text was updated successfully, but these errors were encountered: