We have updated our Terms of Service, Code of Conduct, and Addendum.

Any issues if we made out `prod` branch the default branch in Gitlab?

Options
jinsea
jinsea Posts: 7 ✭
in General Discussions

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

  • Raanan Dagan
    Raanan Dagan Posts: 101 mod
    Options

    hi <@U03ES1W5F3J&gt;! let's see what <@U01J549PR6Y&gt; has to say when he sees this

  • Raanan Dagan
    Raanan Dagan Posts: 101 mod
    Options

    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'

  • jinsea
    jinsea Posts: 7 ✭
    Options

    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?

  • jinsea
    jinsea Posts: 7 ✭
    Options

    ```[Service] Environment=CRIBL_GIT_OPS=push Environment=CRIBL_GIT_BRANCH=prod```

  • Raanan Dagan
    Raanan Dagan Posts: 101 mod
    Options

    'push' means that you cannot update the branch directly from Cribl .. only receive information from the branch

  • jinsea
    jinsea Posts: 7 ✭
    Options

    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?

  • Raanan Dagan
    Raanan Dagan Posts: 101 mod
    Options

    aha .. :smile: .. nothing .. you can use prod as the default

  • jinsea
    jinsea Posts: 7 ✭
    Options

    cool, ty Raanan!

Categories