Introduce Keyword for rollback for Helm K8s

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Release notes

Problem to solve

Looking at a project with Helm Rollback. It didn’t use any of the GitLab UI, but had a manual way of rolling back. If you do it that way, it brings it into a weird state. GitLab and k8s think different things are deployed.

Proposal

Proposal is to introduce a new action for rollback similar to action:prepare.

In this action the user should be able to define the commit SHA to roll back to. An eligant way to do this is by passing the SHA as a CI variable or dotenv variable.

build:
  stage: build
  script:
    - echo "Building the app"
  environment:
    name: staging
    action: rollback
    release: $CI_ROLLBACK

Helm use case:

helm rollback [flags] [RELEASE] [REVISION]

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.

Edited by 🤖 GitLab Bot 🤖