Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: operator-framework/api
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v0.14.0
Choose a base ref
...
head repository: operator-framework/api
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v0.15.0
Choose a head ref
  • 6 commits
  • 18 files changed
  • 4 contributors

Commits on Mar 30, 2022

  1. 🐛 fix channel naming validation (#231) 

    * fix: check for warning when the channel naming does not follow the convention

* applying nit suggestions

* fix-channel-check

* adressing nit review
    @camilamacedo86
    camilamacedo86 authored Mar 30, 2022
    Configuration menu
    Copy the full SHA
    f718c91 View commit details
    Browse the repository at this point in the history

Commits on Apr 5, 2022

  1. Add CRD description check validation (#234) 

    This adds a check to the good practices validator that ensures all CRDs
declared in the bundle have non-empty descriptions. Both owned and
required CRDs will be checked. Note that this validates the CRD
definition in the CSV, not any field in the CRD itself.

Signed-off-by: Ryan King <ryking@redhat.com>
    @ryantking
    ryantking authored Apr 5, 2022
    Configuration menu
    Copy the full SHA
    a7ebc81 View commit details
    Browse the repository at this point in the history

Commits on Apr 13, 2022

  1. Introduce UpgradeStrategy field to OperatorGroups (#235) 

    This commit introduces the upgradeStrategy field to the operatorGroup
type. The upgradeStrategy field defines OLM behavior when upgrading
operators in the namespace. Two upgrade strategies are currently
supported, "Default" and "TechPreviewUnsafeFailForward".

The "Default" strategy mimics existing behavior.

The "TechPreviewUnsafeFailForward" strategy allows users to recover
from failed installPlans or failed clusterServiceVersions, it should
be noted that these upgrades are unsafe and can lead to unpredictable
behavior and potentially dataloss.
    @awgreene
    awgreene authored Apr 13, 2022
    Configuration menu
    Copy the full SHA
    33310d6 View commit details
    Browse the repository at this point in the history

Commits on May 19, 2022

  1. 🌱 good practices validator nit clean up (#240)

    @camilamacedo86
    camilamacedo86 authored May 19, 2022
    Configuration menu
    Copy the full SHA
    8d4b213 View commit details
    Browse the repository at this point in the history

Commits on May 24, 2022

  1. ✨ (GoodPracticesValidator) : new check to warning that authors should… 

    … not create an operator to manage another operator by looking for RBAC permissions to create CRDs (#241)
    @camilamacedo86
    camilamacedo86 authored May 24, 2022
    Configuration menu
    Copy the full SHA
    05acd7a View commit details
    Browse the repository at this point in the history

  2. chore: bump k8s deps to 1.24 & makefile go 1.18 support (#242) 

    * bump k8s deps to 1.24 and go version to 1.18

Signed-off-by: Bryce Palmer <bpalmer@redhat.com>

* revert Go 1.18 bump

Signed-off-by: Bryce Palmer <bpalmer@redhat.com>

* revert go 1.18 in workflows

Signed-off-by: Bryce Palmer <bpalmer@redhat.com>
    @everettraven
    everettraven authored May 24, 2022
    Configuration menu
    Copy the full SHA
    725ffce View commit details
    Browse the repository at this point in the history
Loading