Gitops workflow with isolated production approval gate

Поделиться
HTML-код
  • Опубликовано: 9 ноя 2024

Комментарии • 6

  • @henrikholst7490
    @henrikholst7490 2 года назад

    Why have 3 separate environment files? Keep those separate. Updating prod values shouldn't be a concern for the dev repo. Look into deployment (prod,staging,dev) and service code repo split.

    • @kaihendry
      @kaihendry  2 года назад +2

      I'm against the split, I'm a monorepo kindof guy.
      I want to be clear this second "prd" repo is an anti-pattern, it's just to meet a business requirement.
      Hopefully the requirement will subside and we go back to one repo.

  • @BrianOxleyTexan
    @BrianOxleyTexan 2 года назад

    I would suggest that compliance and change management are strong reasons not to deploy on each commit or several times a day. This is a problem that we advocates for deploy-on-commit have not solved. So are there are valid business requirements to have controlled releases under review by non-tech folks. This is a nut I have not yet seen cracked.

    • @kaihendry
      @kaihendry  2 года назад +1

      You didn't think the second repo idea was good enough to crack the nut? ;)

    • @BrianOxleyTexan
      @BrianOxleyTexan 2 года назад

      @@kaihendry If you're going to have a second repo, why not have a second branch for production? I wonder how to fit these concerns into TBD.
      Modern development is a mixture of modern practices, and not all work together nicely.
      You do talk about branches!

  • @xseman
    @xseman 2 года назад

    it's sad that nowadays we sometimes have to hack the engineering process to please upper management…