Skip to content

Add command for updating olmv1 catalog #232

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

rashmigottipati
Copy link
Member

Adds command to update an existing olmv1 operator (ClusterCatalog).

Command has the following signature and flags:

Update a catalog

Usage:
  operator olmv1 update catalog <catalog> [flags]

Flags:
      --availability-mode string           available means that the catalog should be active and serving data
      -h, --help                               help for catalog
      --labels stringToString              labels that will be added to the catalog (default [])
      --priority int32                     priority determines the likelihood of a catalog being selected in conflict scenarios
      --source-poll-interval-minutes int   catalog source polling interval [in minutes] (default 5)

Global Flags:
  -n, --namespace string   If present, namespace scope for this CLI request
      --timeout duration   The amount of time to wait before giving up on an operation. (default 1m0s)

Example walkthrough:

▶ kubectl get clustercatalog -n olmv1
NAME            LASTUNPACKED   SERVING   AGE
operatorhubio                  False     7d18h
▶ kubectl operator olmv1 update catalog testcatalog --availability-mode=Available
operator "testcatalog" updated
▶ kubectl get clustercatalog -n olmv1
NAME            LASTUNPACKED   SERVING   AGE
testcatalog                  True     7d18h

➜ kubectl operator olmv1 update catalog testcatalog --availability-mode=Available --priority=1 --source-poll-interval-minutes=6
operator "testcatalog" updated

@openshift-ci openshift-ci bot requested review from exdx and jmrodri April 30, 2025 17:45
@rashmigottipati rashmigottipati force-pushed the update-clustercatalog branch 3 times, most recently from b80163c to 930d034 Compare May 1, 2025 03:11
Copy link
Contributor

@ankitathomas ankitathomas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added lgtm Indicates that a PR is ready to be merged. and removed lgtm Indicates that a PR is ready to be merged. labels May 5, 2025
Copy link
Contributor

@ankitathomas ankitathomas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added lgtm Indicates that a PR is ready to be merged. and removed lgtm Indicates that a PR is ready to be merged. labels May 9, 2025
@rashmigottipati rashmigottipati force-pushed the update-clustercatalog branch from 24c16c5 to 94e5778 Compare May 9, 2025 22:07
Copy link
Contributor

@ankitathomas ankitathomas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 13, 2025
@rashmigottipati rashmigottipati force-pushed the update-clustercatalog branch from 03ab15f to 38d2a8a Compare May 13, 2025 18:54
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label May 13, 2025
Copy link
Contributor

@ankitathomas ankitathomas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 13, 2025
@ankitathomas ankitathomas added this pull request to the merge queue May 13, 2025
Merged via the queue into operator-framework:main with commit 8066c73 May 13, 2025
4 checks passed
@rashmigottipati rashmigottipati deleted the update-clustercatalog branch May 13, 2025 19:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants