access-control

Issue split from hasura/graphql-engine#6951

our pytest output has a pretty low signal:noise ratio, and it's often difficult to understand the cause of a test failure, if there is one. [Example: a 8600-line log for what turned out to be a flaky test that passed on a second run](https://app.circleci.com/pipelines/github/hasura/graphql-engine-mono/10008/workflows/5e17c7

With oso 0.11.1 and Rust client code.

When tracking down policy logic failures using the POLAR_LOG=1 environment variable I will see the logging of the execution of all of my inline queries. The problem is that I have lots of these, but usually I'm not interested in the ones in my core policy files which are fairly static and unchanging, but rather I'm interested in those policy sources that

Description: Earlier this year we started work on the Cloud Native Security Map with the goal to provide a practitioner's and learner's guide on navigating the Cloud Native security landscape. Thanks to great work by the STAG community, we are nearing completion of the phase-1 (aka Vanilla version) of the map. More details on that phase can be found in #551.

The Vanilla version of the map f

Projects needed to be implemented:

• https://github.com/casbin-rs/diesel-adapter
• https://github.com/casbin-rs/sqlx-adapter/
• https://github.com/casbin-rs/actix-casbin-auth
• https://github.com/casbin-rs/actix-casbin

Every now and then happens that the instance fails to boot up and it would be good to have a way how to debug it, AWS just provided it. aws-gate should have support for this.

More https://aws.amazon.com/about-aws/whats-new/2021/03/introducing-ec2-serial-console/