Skip to content

0.5.0: Override Access levels so we aren't dependent on incorrect AWS documentation

Choose a tag to compare

View all tags
@kmcquade kmcquade released this 18 Oct 16:08
· 1111 commits to master since this release
0.5.0
387c03a
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

Added

  • We can now override Access levels so we aren't entirely dependent upon accurate AWS documentation for proper ACLs. Fixes #8.
  • Test cases for the new Access level override functions
  • You can now supply a custom YML file as part of the initialize command to test out your own overrides (so you don't have to depend on updates to this repository if you don't want to)
  • Created policy_sentry/shared/data/access-level-overrides.yml for a preloaded set, based on the current known issues with AWS IAM access levels.
  • Cut a new release because this is a big improvement (and because I moved around a function or two)
Assets 2
Loading