-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
SingletonFunction ignores explicit dependencies via node.add_dependency (or node.addDependency) #7568
Labels
Comments
mcalello
added
bug
This issue is a bug.
needs-triage
This issue or PR still needs to be triaged.
labels
Apr 23, 2020
mcalello
changed the title
SingletonFunction ignore explicit dependencies via node.add_dependency (or node.addDependency)
SingletonFunction ignores explicit dependencies via node.add_dependency (or node.addDependency)
Apr 23, 2020
Thanks for filing this issue. This is indeed a problem with I don't think there's a very good workaround for this. You will need to find the Lambda function node from the stack node based on its slug-ified id. |
nija-at
added
p1
and removed
needs-triage
This issue or PR still needs to be triaged.
labels
May 15, 2020
nija-at
pushed a commit
that referenced
this issue
May 15, 2020
The problem here is that the Function construct underlying the SingletonFunction construct is attached directly to the Stack to enforce the Stack-wide singleton behaviour. This commit adds additional methods `addDependencies()` and `dependOn()` methods to let customers declare these. fixes #7568
nija-at
pushed a commit
that referenced
this issue
May 15, 2020
The problem here is that the Function construct underlying the SingletonFunction construct is attached directly to the Stack to enforce the Stack-wide singleton behaviour. This commit adds additional methods `addDependencies()` and `dependOn()` methods to let customers declare these. fixes #7568
mergify bot
pushed a commit
that referenced
this issue
May 15, 2020
…#7997) The problem here is that the Function construct underlying the SingletonFunction construct is attached directly to the Stack to enforce the Stack-wide singleton behaviour. This commit adds additional methods `addDependencies()` and `dependOn()` methods to let customers declare these. fixes #7568
karupanerura
pushed a commit
to karupanerura/aws-cdk
that referenced
this issue
May 22, 2020
…aws#7997) The problem here is that the Function construct underlying the SingletonFunction construct is attached directly to the Stack to enforce the Stack-wide singleton behaviour. This commit adds additional methods `addDependencies()` and `dependOn()` methods to let customers declare these. fixes aws#7568
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Explicitly declaring dependencies with SingletonFunction constructs are silently ignored. This is true in both directions:
Reproduction Steps
Error Log
when I switch to vanilla Function, rather than SingletonFunction for both Lambda1 and Lambda2 I see the expected dependencies present from both Lambda 1, and my Example Role.
Expected Result:
Furthermore, if I leave lambda1 as a SingletonFunction - and make lambda2 a vanilla Function - it will ignore my explicit dependency with lambda1, but recognize my explicit dependency with Example Role:
Environment
Other
I'm not sure this issue is limited to only SingletonFunction constructs.
This is 🐛 Bug Report
The text was updated successfully, but these errors were encountered: