-
Notifications
You must be signed in to change notification settings - Fork 148
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
datasciencepipelines component refactor #1340
Merged
openshift-merge-bot
merged 1 commit into
opendatahub-io:feature-operator-refactor
from
jackdelahunt:datasciencepipelines-refactor
Nov 19, 2024
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -21,26 +21,17 @@ import ( | |
metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" | ||
) | ||
|
||
// EDIT THIS FILE! THIS IS SCAFFOLDING FOR YOU TO OWN! | ||
// NOTE: json tags are required. Any new fields you add must have json tags for the fields to be serialized. | ||
|
||
// DataSciencePipelinesSpec defines the desired state of DataSciencePipelines | ||
type DataSciencePipelinesSpec struct { | ||
// INSERT ADDITIONAL SPEC FIELDS - desired state of cluster | ||
// Important: Run "make" to regenerate code after modifying this file | ||
|
||
// Foo is an example field of DataSciencePipelines. Edit datasciencepipelines_types.go to remove/update | ||
Foo string `json:"foo,omitempty"` | ||
} | ||
|
||
// DataSciencePipelinesStatus defines the observed state of DataSciencePipelines | ||
type DataSciencePipelinesStatus struct { | ||
components.Status `json:",inline"` | ||
} | ||
const ( | ||
DataSciencePipelinesComponentName = "data-science-pipelines-operator" | ||
// value should match whats set in the XValidation below | ||
DataSciencePipelinesInstanceName = "default-datasciencepipelines" | ||
DataSciencePipelinesKind = "DataSciencePipelines" | ||
) | ||
|
||
// +kubebuilder:object:root=true | ||
// +kubebuilder:subresource:status | ||
// +kubebuilder:resource:scope=Cluster | ||
// +kubebuilder:validation:XValidation:rule="self.metadata.name == 'default-datasciencepipelines'",message="DataSciencePipelines name must be default-datasciencepipelines" | ||
|
||
// DataSciencePipelines is the Schema for the datasciencepipelines API | ||
type DataSciencePipelines struct { | ||
|
@@ -51,8 +42,22 @@ type DataSciencePipelines struct { | |
Status DataSciencePipelinesStatus `json:"status,omitempty"` | ||
} | ||
|
||
// DataSciencePipelinesSpec defines the desired state of DataSciencePipelines | ||
type DataSciencePipelinesSpec struct { | ||
DataSciencePipelinesCommonSpec `json:",inline"` | ||
} | ||
|
||
type DataSciencePipelinesCommonSpec struct { | ||
components.DevFlagsSpec `json:",inline"` | ||
} | ||
|
||
// DataSciencePipelinesStatus defines the observed state of DataSciencePipelines | ||
type DataSciencePipelinesStatus struct { | ||
components.Status `json:",inline"` | ||
} | ||
|
||
func (c *DataSciencePipelines) GetDevFlags() *components.DevFlags { | ||
return nil | ||
return c.Spec.DevFlags | ||
} | ||
|
||
func (c *DataSciencePipelines) GetStatus() *components.Status { | ||
|
@@ -71,3 +76,11 @@ type DataSciencePipelinesList struct { | |
func init() { | ||
SchemeBuilder.Register(&DataSciencePipelines{}, &DataSciencePipelinesList{}) | ||
} | ||
|
||
// DSCDataSciencePipelines contains all the configuration exposed in DSC instance for DataSciencePipelines component | ||
type DSCDataSciencePipelines struct { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. same for here |
||
// configuration fields common across components | ||
components.ManagementSpec `json:",inline"` | ||
// datasciencepipelines specific field | ||
DataSciencePipelinesCommonSpec `json:",inline"` | ||
} |
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
176 changes: 0 additions & 176 deletions
176
components/datasciencepipelines/datasciencepipelines.go
This file was deleted.
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we want to use plural?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought for DSP that it is always plural, but maybe I am wrong.
Ray operator == DataSciencePipelines operator ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no, Ray is Ray, DSP is DSP, two different components
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No sorry I didn't mean they are the same, when you refer to ray operator you say Ray, when you refer to DSP operator you say DataSciencePipelines, you use plural not singular. But I could be wrong with that, it is just that I seen that before and I thought I would copy that way
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i was thinking here:
but now i see https://github.com/jackdelahunt/opendatahub-operator/blob/datasciencepipelines-refactor/bundle/manifests/components.opendatahub.io_datasciencepipelines.yaml#L13-L14
both singular and pulural are set to the same value :D
idk, let @lburgazzoli to tell if it should be
kind: DataSciencePipelines
or
kind: DataSciencePipeline