This message originated from Cribl Community Slack.
Click here to view the original link.
If we're implementing Github/Github Ops, should the repo be read-only. If I'm correct, you won't want to modify Cribl through anything but the UI unless it's specific .yaml files on servers right?
Solved
GitHub Audit Logs
Best answer by Ben Marcus
The leader in "dev" will need to push and write commits into the remote repo. I'd suggest having the repo be private but writable and accessible from the leader host. If your using multiple branches then you might need to allow commits and PR between the branches.
Depends on what exactly your trying todo. In your "dev" env you'll want to be able to have Cribl setup with a remote git repo and changes commited and pushed stored in the remote repo. So will need write ability
I mean admins will want to use the UI for most of everything (or CLI). But you won't want to be modifying this from a Github repo and trying to distribute that way right?
The leader in "dev" will need to push and write commits into the remote repo. I'd suggest having the repo be private but writable and accessible from the leader host. If your using multiple branches then you might need to allow commits and PR between the branches.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.