-
Notifications
You must be signed in to change notification settings - Fork 824
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
fix: changing pinpoint policy #5918
Conversation
Codecov Report
@@ Coverage Diff @@
## master #5918 +/- ##
========================================
Coverage 58.13% 58.13%
========================================
Files 413 413
Lines 18886 18886
Branches 3573 3771 +198
========================================
Hits 10980 10980
+ Misses 7244 7224 -20
- Partials 662 682 +20
Continue to review full report at Codecov.
|
@nikhname, @kaustavghosh06 -- This change has caused customer issues on the client side, because customers can no longer remove endpoints once they hit the 10 endpoint limit. What is the expectation for customers to be able to remove endpoints? |
+1, facing same issues as @palpatim |
Having the same issue. Why was getUserEndpoints removed? |
this appears to be a corresponding JS library change aws-amplify/amplify-js#7245 |
Can we please get this and the corresponding change in js reverted? This is causing all sorts of problems... |
@ammarkarachi and @nikhname can you please give us some reasoning why this was done and what is being done to resolve this? |
Are we just going to leave this broken? |
This is a serious issue that is causing a lot of problems. |
Issue #, if available:
Description of changes:
Change in pinpoint policy actions based on discussion
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.