Any issues if we made out `prod` branch the default branch in Gitlab?
Good morning all! When working with GitOps would there be any issues if we made out `prod` branch the default branch in Gitlab? Figured no need for the main if we are only working in `prod` and `non-prod`
Answers
-
hi <@U03ES1W5F3J>! let's see what <@U01J549PR6Y> has to say when he sees this
0 -
No issue .. i.e. as long as CRIBL_GIT_OPS is set to 'none' It is an issue if the goal is to make your Production read only .. i.e. CRIBL_GIT_OPS set to 'push'
0 -
Ahh OK, yes we do have `CRIBL_GIT_OPS=push` set via `systemctl edit cribl` on the prod leader for read-only. Do you happen to know why it would cause an issue?
0 -
```[Service] Environment=CRIBL_GIT_OPS=push Environment=CRIBL_GIT_BRANCH=prod```
0 -
'push' means that you cannot update the branch directly from Cribl .. only receive information from the branch
0 -
Yes correct, but what does that have to do with having the default branch in Gitlab be our `prod` branch vs the unused `main` branch?
0 -
aha .. .. nothing .. you can use prod as the default
0 -
cool, ty Raanan!
0