#
acls
Here are 22 public repositories matching this topic...
Trigger is a robust network automation toolkit written in Python that was designed for interfacing with network devices.
-
Updated
Apr 20, 2021 - Python
A solution to help you build automation and gitops in your Apache Kafka deployments. The Kafka gitops!
-
Updated
Feb 9, 2022 - Java
kafka
acls
kafka-manager
kafka-cluster
gitops
acl-management
kafka-topics
kafka-acls
kafka-dsf
kafka-gitops
-
Updated
Sep 21, 2021 - Java
Rights and roles management for AEM made easy
-
Updated
Jan 19, 2022 - Java
Role-based Authorizations library for Node.js
-
Updated
Aug 10, 2021 - JavaScript
Kattlo CLI Project
java
kafka
native
kafka-consumer
schemas
kafka-connect
apache-kafka
kafka-producer
graalvm
kafka-streams
acls
migration-tool
mtls
quarkus
ksqldb
kattlo
kafka-configurations
-
Updated
Jan 26, 2022 - Java
picatz
commented
Mar 3, 2022
Client agents do not need to enable connect, this is only used on servers:
Enabling Connect requires changing the configuration of only your Consul servers (not client agents).
Serv
Secure Kafka Cluster with DIY Monitoring solution
ssl
elasticsearch
vagrant
kibana
logstash
monitoring
cluster
filebeat
grafana
diamond
acl
elk
grafana-dashboard
acls
graphite-carbon
jmxtrans-agent
elk-stack
kafka-cluster
burrow
kafka-overview
-
Updated
Sep 21, 2021 - Jinja
-
Updated
Jul 1, 2021 - Java
Set ACL recursively on files and folder from an easy to read configuration
-
Updated
Jun 4, 2021 - Swift
Terraform Module AWS S3 Bucket
-
Updated
Dec 16, 2021 - HCL
Proyecto tercer parcial REDES
-
Updated
Jun 17, 2020
Ruah is a practice of how to create your own MVC framework using php.
-
Updated
Jan 11, 2022 - PHP
An app for learning ACLS algorithms by Pacific Medical Training
-
Updated
Apr 9, 2021 - Swift
An ansible role to run the Kafka Topology Builder
-
Updated
Jun 13, 2020
Improve this page
Add a description, image, and links to the acls topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the acls topic, visit your repo's landing page and select "manage topics."
It appears that the flood protection does not check to determine who is sending the event and/or what type of event it is. This means that if a room mod sends redact or ban events "manually" (e.g., via their client, without going through Mjolnir), the bot may ban them for "spamming".
Steps to reproduce the behavior:
Be a mod in a room. Have some other users send a bunch of messages. Then go