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

fix: Remove duplication around plugins' names #1564

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

mateusoliveira43
Copy link
Contributor

Why the changes were made

Noted that we use one variable to define what plugins' names DPA accepts, and another in validators. I was afraid this could haunt us in the future.

How to test the changes made

I ran commands like grep -Inr '"aws"' . and grep -Inr "'aws'" . (ignoring tests folder) to make sure all occurrences were changed.

@openshift-ci openshift-ci bot requested review from mpryc and sseago October 17, 2024 18:26
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 17, 2024
switch provider {
case AWSProvider, "velero.io/aws":
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I you run grep -Inr '"velero.io/aws"' ., you will note only place this is used (aside from test files) is here. Should we remove this and only allow aws?

Copy link
Member

Choose a reason for hiding this comment

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

only allow aws

so velero.io/aws would not work? cause that's what people who move from upstream velero would expect to use.

}

// check for invalid config key
for key := range vslSpec.Velero.Config {
valid := validAWSKeys[key]
if !valid {
return false, fmt.Errorf("DPA %s.config key %s is not a valid %s config key", veleroVSLYAMLPath, key, AWSProvider)
return false, fmt.Errorf("DPA %s.config key %s is not a valid %s config key", veleroVSLYAMLPath, key, string(oadpv1alpha1.DefaultPluginAWS))
}
}
//checking the aws plugin, if not present, throw warning message
Copy link
Contributor Author

Choose a reason for hiding this comment

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

comments are outdated, remove them

@weshayutin
Copy link
Contributor

/retest

@kaovilai
Copy link
Member

2024/11/13 02:35:58 VM cirros-test/cirros-test status is: WaitingForVolumeBinding

common failure

/override ci/prow/4.17-e2e-test-kubevirt-aws

Copy link

openshift-ci bot commented Nov 13, 2024

@kaovilai: Overrode contexts on behalf of kaovilai: ci/prow/4.17-e2e-test-kubevirt-aws

In response to this:

2024/11/13 02:35:58 VM cirros-test/cirros-test status is: WaitingForVolumeBinding

common failure

/override ci/prow/4.17-e2e-test-kubevirt-aws

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Copy link

openshift-ci bot commented Nov 13, 2024

@mateusoliveira43: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Copy link

openshift-ci bot commented Nov 14, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mateusoliveira43, weshayutin

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants