Skip to content

Conversation

@Miciah
Copy link
Contributor

@Miciah Miciah commented Sep 26, 2022

Change the json tag for the recently added LoadBalancer field from "loadbalancer" to "loadBalancer" for consistency with other APIs.

Follow-up to #1209.

  • config/v1/types_ingress.go (IngressSpec): Change "loadbalancer" to "loadBalancer".
  • config/v1/0000_10_config-operator_01_ingress.crd.yaml:
  • config/v1/zz_generated.swagger_doc_generated.go:
  • openapi/generated_openapi/zz_generated.openapi.go:
  • openapi/openapi.json: Regenerate.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 26, 2022

Hello @Miciah! Some important instructions when contributing to openshift/api:
API design plays an important part in the user experience of OpenShift and as such API PRs are subject to a high level of scrutiny to ensure they follow our best practices. If you haven't already done so, please review the OpenShift API Conventions and ensure that your proposed changes are compliant. Following these conventions will help expedite the api review process for your PR.

For merging purposes, this repository follows the no-Feature-Freeze process which means that in addition to the standard lgtm and approved labels this repository requires either:

bugzilla/valid-bug - applied if your PR references a valid bugzilla bug

OR

qe-approved, docs-approved, and px-approved - these labels can be applied by anyone in the openshift org via the /label <labelname> command.

Who should apply these qe/docs/px labels?

  • For a no-Feature-Freeze team who is merging a feature before code freeze, they need to get those labels applied to their api repo PR by the appropriate teams (i.e. qe, docs, px)
  • For a Feature Freeze (traditional) team who is merging a feature before FF, they can self-apply the labels (via /label commands), they are basically irrelevant for those teams
  • For a Feature Freeze team who is merging a feature after FF, the PR should be rejected barring an exception

@openshift-ci openshift-ci bot requested review from knobunc and sttts September 26, 2022 14:31
@Miciah Miciah force-pushed the NE-799-config-slash-ingress-loadbalancer→loadBalancer branch from 434953e to 05317c2 Compare September 27, 2022 01:47
Change the json tag for the recently added LoadBalancer field from
"loadbalancer" to "loadBalancer" for consistency with other APIs.

Follow-up to commit a86e43a.

This commit is related to NE-799.

https://issues.redhat.com/browse/NE-799

* config/v1/types_ingress.go (IngressSpec): Change "loadbalancer" to
"loadBalancer".
* config/v1/0000_10_config-operator_01_ingress.crd.yaml:
* config/v1/zz_generated.swagger_doc_generated.go:
* openapi/generated_openapi/zz_generated.openapi.go:
* openapi/openapi.json: Regenerate.
@Miciah Miciah force-pushed the NE-799-config-slash-ingress-loadbalancer→loadBalancer branch from 05317c2 to 24ee13c Compare September 27, 2022 01:50
@Miciah
Copy link
Contributor Author

Miciah commented Sep 27, 2022

/test integration

@miheer
Copy link
Contributor

miheer commented Sep 27, 2022

Hi @Miciah! I tested this with the installer but the units test fail.

git clone installer code
cd installer
git rebase origin/master

GO111MODULE=on GOFLAGS=-mod=vendor go mod edit -replace=github.com/openshift/api=github.com/Miciah/api@24ee13c

go mod tidy
go mod vendor

Unit test

[miheer@localhost installer]$ GO111MODULE=on go test -v -run Test  ./pkg/asset/manifests/...
# k8s.io/client-go/tools/record
vendor/k8s.io/client-go/tools/record/event.go:301:13: assignment mismatch: 1 variable but e.Watch returns 2 values
vendor/k8s.io/client-go/tools/record/event.go:349:13: assignment mismatch: 1 variable but recorder.ActionOrDrop returns 2 values
FAIL	github.com/openshift/installer/pkg/asset/manifests [build failed]
?   	github.com/openshift/installer/pkg/asset/manifests/alibabacloud	[no test files]
=== RUN   TestCloudProviderConfig
--- PASS: TestCloudProviderConfig (0.00s)
PASS
ok  	github.com/openshift/installer/pkg/asset/manifests/azure	(cached)
=== RUN   TestCloudProviderConfig
--- PASS: TestCloudProviderConfig (0.00s)
=== RUN   TestCloudProviderConfigWithNPID
--- PASS: TestCloudProviderConfigWithNPID (0.00s)
PASS
ok  	github.com/openshift/installer/pkg/asset/manifests/gcp	(cached)
=== RUN   TestCloudProviderConfig
=== RUN   TestCloudProviderConfig/default_subnet_config
=== RUN   TestCloudProviderConfig/existing_subnet_config
--- PASS: TestCloudProviderConfig (0.00s)
    --- PASS: TestCloudProviderConfig/default_subnet_config (0.00s)
    --- PASS: TestCloudProviderConfig/existing_subnet_config (0.00s)
PASS
ok  	github.com/openshift/installer/pkg/asset/manifests/ibmcloud	(cached)
FAIL	github.com/openshift/installer/pkg/asset/manifests/openstack [build failed]
?   	github.com/openshift/installer/pkg/asset/manifests/powervs	[no test files]
=== RUN   TestCloudProviderConfig
=== RUN   TestCloudProviderConfig/valid_in-tree_cloud_provider_config
=== RUN   TestCloudProviderConfig/valid_out_of_tree_cloud_provider_config
[Global]
secret-name = "vsphere-creds"
secret-namespace = "kube-system"
insecure-flag = "1"

[VirtualCenter "test-vcenter"]
port = "443"

datacenters = "test-datacenter,test-datacenter2"

[Workspace]
folder = "/test-datacenter/vm/clusterID"

[Labels]
region = "openshift-region"
zone = "openshift-zone"

--- PASS: TestCloudProviderConfig (0.00s)
    --- PASS: TestCloudProviderConfig/valid_in-tree_cloud_provider_config (0.00s)
    --- PASS: TestCloudProviderConfig/valid_out_of_tree_cloud_provider_config (0.00s)
PASS
ok  	github.com/openshift/installer/pkg/asset/manifests/vsphere	(cached)
FAIL
[miheer@localhost installer]$

@deads2k
Copy link
Contributor

deads2k commented Sep 27, 2022

/approve
/hold

holding so @Miciah can chase usage and be sure the change will work.

@openshift-ci openshift-ci bot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Sep 27, 2022
@lihongan
Copy link
Contributor

/label qe-approved

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Sep 28, 2022
@CFields651
Copy link

/label px-approved

@openshift-ci openshift-ci bot added the px-approved Signifies that Product Support has signed off on this PR label Sep 28, 2022
@Miciah
Copy link
Contributor Author

Miciah commented Sep 28, 2022

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 28, 2022
@ahardin-rh
Copy link

/label docs-approved

@miheer
Copy link
Contributor

miheer commented Sep 29, 2022

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 29, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 29, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deads2k, Miciah, miheer

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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 29, 2022

@Miciah: 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/test-infra repository. I understand the commands that are listed here.

@openshift-merge-robot openshift-merge-robot merged commit 18c2982 into openshift:master Sep 29, 2022
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. docs-approved Signifies that Docs has signed off on this PR lgtm Indicates that a PR is ready to be merged. px-approved Signifies that Product Support has signed off on this PR qe-approved Signifies that QE has signed off on this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants