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

no-jira: build: drop vsphereprivate build workaround #7847

Merged
merged 1 commit into from Dec 15, 2023

Conversation

r4f4
Copy link
Contributor

@r4f4 r4f4 commented Dec 15, 2023

Initially we were using the provider's module version in the go.sum file to determine if a provider needed to be rebuilt. Since vsphereprivate is locally developed, not an imported module, it required special treatment. Now that we are using the go.mod git hash to check if a terraform provider needs to be rebuilt, we don't need to give vsphereprivate special treatment. Unfortunately, this implementation detail slipped through even though we changed the approach.

If we don't drop the workaround, the build script will think vsphereprivate always needs to be rebuilt since it's comparing values that will never match.

Initially we were using the provider's module version in the go.sum
file to determine if a provider needed to be rebuilt. Since
vsphereprivate is locally developed, not an imported module, it required
special treatment. Now that we are using the `go.mod` git hash to check
if a terraform provider needs to be rebuilt, we don't need to give
vsphereprivate special treatment. Unfortunately, this implementation
detail slipped through even though we changed the approach.

If we don't drop the workaround, the build script will think
`vsphereprivate` always needs to be rebuilt since it's comparing values
that will never match.
@patrickdillon
Copy link
Contributor

/approve
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 15, 2023
Copy link
Contributor

openshift-ci bot commented Dec 15, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: patrickdillon

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 openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 15, 2023
@r4f4
Copy link
Contributor Author

r4f4 commented Dec 15, 2023

2023-12-15T17:38:01.190842315Z + version_info=6c00811dcb1d45e5271dda78e5dad9f6693b1efb
2023-12-15T17:38:01.191490969Z ++ git hash-object terraform/providers/vsphereprivate/go.mod
2023-12-15T17:38:01.193921650Z + test 6c00811dcb1d45e5271dda78e5dad9f6693b1efb == 6c00811dcb1d45e5271dda78e5dad9f6693b1efb
2023-12-15T17:38:01.194030054Z + echo 'vsphereprivate is up-to-date'
2023-12-15T17:38:01.194108717Z vsphereprivate is up-to-date

Looking good.

/retitle no-jira: build: drop vsphereprivate build workaround

@openshift-ci openshift-ci bot changed the title build: drop vsphereprivate build workaround no-jira: build: drop vsphereprivate build workaround Dec 15, 2023
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Dec 15, 2023
@openshift-ci-robot
Copy link
Contributor

@r4f4: This pull request explicitly references no jira issue.

In response to this:

Initially we were using the provider's module version in the go.sum file to determine if a provider needed to be rebuilt. Since vsphereprivate is locally developed, not an imported module, it required special treatment. Now that we are using the go.mod git hash to check if a terraform provider needs to be rebuilt, we don't need to give vsphereprivate special treatment. Unfortunately, this implementation detail slipped through even though we changed the approach.

If we don't drop the workaround, the build script will think vsphereprivate always needs to be rebuilt since it's comparing values that will never match.

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.

Copy link
Contributor

openshift-ci bot commented Dec 15, 2023

@r4f4: 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-bot openshift-merge-bot bot merged commit 611e16a into openshift:master Dec 15, 2023
20 checks passed
@r4f4 r4f4 deleted the rebuild-tf-providers-fix branch December 15, 2023 18:32
@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-installer-altinfra-container-v4.16.0-202312160051.p0.g611e16a.assembly.stream for distgit ose-installer-altinfra.
All builds following this will include this PR.

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. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants