-
Notifications
You must be signed in to change notification settings - Fork 76
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
feat(data): Add stack mapping to AmplifyData for limit issue #2012
base: main
Are you sure you want to change the base?
Conversation
🦋 Changeset detectedLatest commit: fd678af The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Hey @sobolk, any news from here? We need this for big projects |
Hey @MarlonJD 👋 thank you for your continued patience with us 🙂 we're going to update the tagged release that surfaces this prop with the latest from |
Hey @josefaidt, 👋 thanks for the update! I’m looking forward to the tagged release. If the map stack comes through quickly, that’d be great, but resolving the issue without it sounds promising as well. Ultimately, having the sandboxes fully functional is something I’m really excited about, and I can’t wait to see it in action! |
I've created a snapshot of this PR rebased on the current main branch.
|
Thank you so much @dpilch for providing the snapshots, this will be incredibly helpful for my current tasks. I really appreciate you thinking ahead and taking the time to prepare these for me. |
Problem
Issue number, if available:
aws-amplify/amplify-category-api#2550
Changes
I added stackMapping to gen2 amplify-backend, we need this parameter like in gen1 for limit issue
Validation
Checklist
run-e2e
label set.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.