fleet icon indicating copy to clipboard operation
fleet copied to clipboard

Add ability to sync multiple branches/refs / Git labels

Open shane-davidson opened this issue 3 years ago • 0 comments

Rather that having a single ref would it be possible to sync a list of refs/branches (or all) using fleet?

Each ref would then create it's own bundle.

Uses cases for this involve software development and having multiple deployments of the same code based on commits/branches.

Injecting the ref-name into the helm chart would then also be required. maybe in the form of gitLabels?

global.fleet.gitLabels.management.cattle.io/commit-ref-name global.fleet.gitLabels.management.cattle.io/commit-sha global.fleet.gitLabels.management.cattle.io/commit-sha-short global.fleet.gitLabels.management.cattle.io/repo-url global.fleet.gitLabels.management.cattle.io/commit-timestamp etc

This would allow:

  • deploying a bundle per git ref
  • deploying the same code to different namespaces per git ref
  • deploying multiple instances of resources per git ref

for example: if you have a web/saas product and need a UAT/testing environment you could deploy the following resources:

namespace <ref-name> ingress <ref-name>.domain deployment/container with image image_name:<image tag using the ref-name>

Each new branch a developer creates will then automatically spin up a new live/test instance of the environment

This functionality would greatly improve/facilitate the development/testing lifecycle when multiple instances of same repo are needed (e.g. development vs main/production)

Even just adding the git labels would allow creating multiple git repos that track different branches of the same repo and then reference the branch/commit etc.

shane-davidson avatar Jun 29 '22 00:06 shane-davidson