Demo for the Trust marketing launch. This includes Confluent Cloud audit logs, data plane role based access control (RBAC), and bring your own key (BYOK).
WARNING: This pull request will be forcibly merged on April 1st, 2022 (4/1) in it's current state if no action is taken...
Background
As recently communicated the Tools, IT and Information Security teams will be enforcing a series of standardized access controls in Github that will impact this GitHub repository.
Each repository will be required to have a valid set of code owners who are reponsible for reviewing/approving pull requests.
Description
This pull request introduces a list of owners that has been auto-generated based on the teams with admin/pull permissions to this repository. A preference has been given to GitHub Teams over individual users where possible.
Impact
Immediately after this pull request is merged, the specified code owners will be auto-assigned to any newly created pull requests.
Unless the repository already has the relevant branch protection rules configured, an approval/review from these code owner will not be required to merge a pull request. However, as communicated we intend to enable such branch protection requirements for each repository on May 1st, 2022 (5/1).
Required Actions
If this list is incomplete/inaccurate, you must update the file by clicking Edit file in the GitHub UI for this branch/pull request and making the necessary changes.
There are 100s of these auto-generated pull requests and comments/'suggested changes' will not be addressed, you must directly commit the changes.
Similarly, once the file is ready to be merged, you must actively merge the pull request in the GitHub UI. It will not be auto-merged after approvals/comments are added.
WARNING: This pull request will be forcibly merged on
April 1st, 2022(4/1) in it's current state if no action is taken...Background
As recently communicated the Tools, IT and Information Security teams will be enforcing a series of standardized access controls in Github that will impact this GitHub repository.
Each repository will be required to have a valid set of code owners who are reponsible for reviewing/approving pull requests.
Description
This pull request introduces a list of owners that has been auto-generated based on the teams with admin/pull permissions to this repository. A preference has been given to GitHub Teams over individual users where possible.
Impact
Immediately after this pull request is merged, the specified code owners will be auto-assigned to any newly created pull requests.
Unless the repository already has the relevant branch protection rules configured, an approval/review from these code owner will not be required to merge a pull request. However, as communicated we intend to enable such branch protection requirements for each repository on
May 1st, 2022(5/1).Required Actions
If this list is incomplete/inaccurate, you must update the file by clicking
Edit filein the GitHub UI for this branch/pull request and making the necessary changes.There are 100s of these auto-generated pull requests and comments/'suggested changes' will not be addressed, you must directly commit the changes.
Similarly, once the file is ready to be merged, you must actively merge the pull request in the GitHub UI. It will not be auto-merged after approvals/comments are added.
Questions?
If you have any questions, please read the FAQs and/or reach out on slack at #github-access-controls.