-
Notifications
You must be signed in to change notification settings - Fork 14
Deprecate KindOverride fields and use internal api group. #531
Conversation
Skipping CI for Draft Pull Request. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jiachengxu 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 |
/retest |
2 similar comments
/retest |
/retest |
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.
looks good, I just think it's better to use constants in test
@@ -135,7 +135,7 @@ func TestCustomResourceDiscoveryReconciler(t *testing.T) { | |||
|
|||
internalCRD := &apiextensionsv1.CustomResourceDefinition{} | |||
require.NoError(t, r.Client.Get(ctx, types.NamespacedName{ | |||
Name: strings.Join([]string{"redis", serviceClusterName, crDiscovery.Namespace}, "."), | |||
Name: strings.Join([]string{"redis", "internal", serviceClusterName, crDiscovery.Namespace}, "."), |
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.
why not using constant here?
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.
fixed here.
test/integration/apiserver.go
Outdated
@@ -380,14 +378,14 @@ func instanceService(ctx context.Context, conn *grpc.ClientConn, tenantAccount * | |||
offering := &catalogv1alpha1.Offering{ | |||
ObjectMeta: metav1.ObjectMeta{ | |||
Namespace: tenantAccount.Status.Namespace.Name, | |||
Name: strings.Join([]string{"dbs", serviceCluster.Name, providerAccount.Name}, "."), | |||
Name: strings.Join([]string{"dbs", "external", serviceCluster.Name, providerAccount.Name}, "."), |
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.
same here
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.
We cannot use constants pkg in test, since constants are under internal
package.
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.
that is sad
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.
hmm, if needed, we can move the whole constants package out of internal, what do you think?
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.
it's not a big deal, I'm ok to merge it as is, but yeah, I think constants should not be in the internals
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.
OK, let's do it in a dedicated PR and move the whole constants pkg out of internal
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.
👍
/lgtm |
LGTM label has been added. Git tree hash: b14fdcff9d074537f6db0b2d9d8f126f8804d1d8
|
/hold |
/retest |
/unhold |
/lgtm |
LGTM label has been added. Git tree hash: 236dbc7b1dd4678585878a4685b53098e8c2f01c
|
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #
Special notes for your reviewer:
Documentation:
Does this PR introduce a user-facing change?: