amplify-backend
amplify-backend copied to clipboard
[POC] Use single stack for top level functions
Problem
Certain usage patterns of functions end up with Caused By: ❌ Deployment failed: Error [ValidationError]: Circular dependency between resources:.
This happens is scenarios where it could have been avoided. Just because we pack all functions into same stack and therefore coupling them together.
Changes
This PR explores potential mitigation of the problem in a form of a knob that makes backend to put all top level resources in single stack.
I.e.
const backend = defineBackend({
auth,
data,
myApiFunction,
},{
useSingleStack: true,
});
Validation
There are two test projects used to reproduce the original problem:
test-projects/function-stack-1test-projects/function-stack-2
Both deployed successfully with new setting.
Checklist
- [ ] If this PR includes a functional change to the runtime behavior of the code, I have added or updated automated test coverage for this change.
- [ ] If this PR requires a change to the Project Architecture README, I have included that update in this PR.
- [ ] If this PR requires a docs update, I have linked to that docs PR above.
- [ ] If this PR modifies E2E tests, makes changes to resource provisioning, or makes SDK calls, I have run the PR checks with the
run-e2elabel set.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
⚠️ No Changeset found
Latest commit: 59735d941fb3492c511a07b83b41aa4d399b814f
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR