Closed nagavijayan-nagarathinam closed 1 month ago
Hi @nagavijayan-nagarathinam ! I just try reproduce the issue with the latest AWS Provider Version(v0.31.0) and seems can't reproduce it.
I used next example file with 40 resources:
apply this file and then checked that all resources created correctly:
Could yo please try to reproduce this issue once again with the latest AWS Provider Version(v0.31.0) and if it will reproduced - please attach yaml with tested resource?
This provider repo does not have enough maintainers to address every issue. Since there has been no activity in the last 90 days it is now marked as stale
. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh
will mark this issue as not stale.
This issue is being closed since there has been no activity for 14 days since marking it as stale
. If you still need help, feel free to comment or reopen the issue!
What happened ?
I am tring to create group of IAM and securityGroup resources together, thats comes around totally 40 manage resources. it was able to keep sync state successful and everything looks good, Only when resource count is 20 to 25 at a time
But when the overall resource count goes beyond 30, i started to get this error messages in all the MR status.
How can we reproduce it?
Write 40 series of managed resource in a file combination of IAM role/policy/attachments SecurityGroups/Rules and apply that to reproduce it
What environment did it happen in?
Include at least the version or commit of Official AWS Provider you were running. Consider
also including your:
kubectl version
) - v1.23same error message getting across the resources