Skip to content

OpenShift operator PR

Actions
Submit PRs to OpenShift operator repositories
v1
Latest
Star (1)

⛑️ openshift-operator-pr

CI

GitHub action to submit PRs to OpenShift operator repositories.

Operator repositories

Before using this action

  • Fork the operator repositories you are willing to submit your operator to.
  • Get a GitHub PAT with write access to the previous repo.

Usage

name: Release

on:
  push:
    tags:
      - "*"

jobs:
  operator-pr:
    name: Version
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v4
        with:
          fetch-depth: 0

      - name: Fetch tags
        run: git fetch --force --tags

      - name: Get Version
        id: version
        run: |
          VERSION=sha-${GITHUB_SHA::8}
          if [[ $GITHUB_REF == refs/tags/* ]]; then
            VERSION=${GITHUB_REF/refs\/tags\//}
          fi
          echo ::set-output name=version::${VERSION}

      # TODO:
      # - Generate bundle
      # - Push bundle image to a registry

      - name: Operator PR
        uses: mariadb-operator/openshift-operator-pr@v1
        env:
          GITHUB_TOKEN: "${{ secrets.GITHUB_TOKEN }}"
        with:
          name: "mariadb-operator"
          version: "${{ steps.version.outputs.version }}"
          fork-repo-name: "mariadb-operator/community-operators"
          upstream-repo-name: "k8s-operatorhub/community-operators"
          bundle-path-dir: "deploy/olm"
          ci-path-file: "deploy/olm/ci.yaml"
          user-name: "Martin Montes"
          user-email: "[email protected]"

Note

The paths provided in the previous example match the manifests available in the current repository.

Example PRs

OpenShift operator PR is not certified by GitHub. It is provided by a third-party and is governed by separate terms of service, privacy policy, and support documentation.

About

Submit PRs to OpenShift operator repositories
v1
Latest

OpenShift operator PR is not certified by GitHub. It is provided by a third-party and is governed by separate terms of service, privacy policy, and support documentation.