Skip to content

Commit

Permalink
[WIP] Adding Availability enum to catalog spec
Browse files Browse the repository at this point in the history
Signed-off-by: Lalatendu Mohanty <lmohanty@redhat.com>
  • Loading branch information
LalatenduMohanty committed Oct 3, 2024
1 parent 29d21c7 commit 401f2d0
Showing 1 changed file with 8 additions and 0 deletions.
8 changes: 8 additions & 0 deletions api/core/v1alpha1/clustercatalog_types.go
Original file line number Diff line number Diff line change
Expand Up @@ -92,6 +92,14 @@ type ClusterCatalogSpec struct {
// +kubebuilder:default:=0
// +optional
Priority int32 `json:"priority"`

// Availability is an optional field that allows users to define whether the ClusterCatalog is utilized by the operator-controller.
// If set to "Enabled", the catalog will be used for updates, serving contents, and package installations.
// If set to "Disabled", the catalog will be ignored by the operator-controller, meaning it will not be used for any operations.
// +kubebuilder:validation:Enum="Disabled";"Enabled"
// +kubebuilder:default="Enabled"
// +optional
Availability string `json:"availability,omitempty"`
}

// ClusterCatalogStatus defines the observed state of ClusterCatalog
Expand Down

0 comments on commit 401f2d0

Please sign in to comment.