Skip to content
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

Improve custom artifact script handling. #20

Merged
merged 2 commits into from
Feb 21, 2023

Conversation

HumairAK
Copy link
Contributor

This change will make it so api server will fail to deploy if a custom artifact script provided by the user does not exist. Furthermore, it will also ensure that the default artifact script follows naming conventions that are consistent with the rest of the namespace scoped resources. Tests are addded to accomodate this change.

Description

Resolve #19

How Has This Been Tested?

Via unit tests, and live ocp cluster.

Merge criteria:

  • The commits are squashed in a cohesive manner and have meaningful messages.
  • Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
  • The developer has manually tested the changes and verified that the changes work

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 16, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: HumairAK

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Since the recently updated cr spec has not had its respective code
changes to make it go into effect, we should keep the old cr spec
present as before. In this change the proposed cr spec is named as such.

Signed-off-by: Humair Khan <humair88@hotmail.com>
This change will make it so api server will fail to deploy if a custom
artifact script provided by the user does not exist. Furthermore, it
will also ensure that the default artifact script follows naming
conventions that are consistent with the rest of the namespace scoped
resources. Tests are addded to accomodate this change.

Signed-off-by: Humair Khan <humair88@hotmail.com>
@HumairAK
Copy link
Contributor Author

This pr did not have the code changes to go along with it. This was resulting in a conflict with this pr which is applying a change to the original cr spec.

I've added another commit that keeps the old cr spec as the standard until another follow up pr to #8 with the code changes takes effect. The proposed cr spec is also kept but the file is named as such.

Copy link
Member

@DharmitD DharmitD left a comment

Choose a reason for hiding this comment

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

Checked the old spec in #8 and verified the changes.

/lgtm

@openshift-ci openshift-ci bot added the lgtm label Feb 21, 2023
@openshift-merge-robot openshift-merge-robot merged commit 0254377 into opendatahub-io:main Feb 21, 2023
dsp-developers pushed a commit to dsp-developers/data-science-pipelines-operator that referenced this pull request Aug 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add better handling of custom artifact script
3 participants