-
Updated
Dec 2, 2020 - Python
iam
Here are 473 public repositories matching this topic...
-
Updated
Oct 28, 2020 - Shell
-
Updated
Nov 19, 2020 - Go
-
Updated
Nov 23, 2020 - Go
Currently, the "future-proofing" unit testing strategy is buried in a GitHub PR comment, which amounts to "tribal knowledge." salesforce/policy_sentry#254 (comment)
To avoid the negative effects of tribal knowledge on OSS governance, we should move this to the documentation under the contribution section.
-
Updated
Jun 21, 2019 - TypeScript
-
Updated
Dec 1, 2020 - JavaScript
-
Updated
Dec 2, 2020 - Java
-
Updated
Sep 25, 2020 - Shell
-
Updated
Feb 15, 2020 - Java
Gotta make sure this tool works across multiple operating systems and Python versions. The biggest concern is the graph file-storage, since that's OS-specific code and I could only test against Ubuntu 16.
Principal Mapper needs to be tested on the following operating systems and Python versions (but not all combinations of which):
Python
- Python 3.6
- Python 3.7
Operati
-
Updated
Nov 26, 2020 - HCL
-
Updated
Nov 27, 2020 - Python
#22 introduced a feature to guess actions that are similar to an existing policy. It currently doesn't support all actions.
Here's things I currently know are missing (comment if you find more):
- KMS:
Encrypt,Decrypt,GenerateDataKey, ... - ECR:
BatchDeleteImage,BatchGetImage, ... -
*Deregister* -
*Modify* -
*Remove* - API Gateway: (
DELETE,
-
Updated
Nov 29, 2020 - Python
-
Updated
May 28, 2020
-
Updated
Aug 2, 2020 - Go
-
Updated
Dec 1, 2020 - Python
-
Updated
Sep 23, 2020 - Go
-
Updated
Oct 13, 2020 - Python
-
Updated
Dec 2, 2020 - Java
-
Updated
Feb 10, 2020 - Python
-
Updated
Jul 16, 2018
Improve this page
Add a description, image, and links to the iam topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the iam topic, visit your repo's landing page and select "manage topics."


Is your feature request related to a problem? Please describe.
As observed during #261, users can accidentally set timeouts inconsistently. A concrete example is that one can set a User facing timeout lower than any backend timeout, such that requests may fail early.
Describe the solution you'd like
We should provide some sanity checking to prevent unintended timeout behavior.