Disconnect gitops from the main branch

[nacx]

Having gitops in the main branch is a bit inconvenient, as demos that use gitops will end up messing the main git tree.

As an alternative, we could probably better configure gitops to rely on custom branches, or even custom forks, to better disconnect custom temporal tweaks from the main repo. This could be something configurable, defaulting to a demo-configs branch, but still allow the ArgoCD module to configure a fork+branch as an alternative.

[smarunich]

I am working on re-factoring argocd, i will keep you posted. The goal is to expose the variables to allow to map the "user-defined" applications to the target clusters.

Envision something like this:

    "argocd_applications": {
        "properties": { "url": ""},
        "tsb": {
        },
        "bookinfo": [
            {
                "cloud": "gcp",
                "cluster_id": 0
            },
            {
              "cloud": "gcp",
              "cluster_id": 1
          }
        ],
        "eshop": [
            {
                "cloud": "azure",
                "cluster_id": 0
            },
            {
              "cloud": "azure",
              "cluster_id": 1
          }
        ]
    }

[boeboe]

May I suggest to use this repo only as a blueprint for gitops driven applications. The TF scripts can spin up a seperate VM with a git server (my suggestion is gogs, a GoLang based lightweight git server) that hosts these apps instead. This way demos doing changes in git-gogs won't affect others and more flexibility is offered in terms of application to cluster mapping.