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

Upgrade support modules to go1.21 #243

Merged
merged 11 commits into from
Jun 10, 2024
Merged

Conversation

thepetk
Copy link
Contributor

@thepetk thepetk commented May 29, 2024

Please specify the area for this PR

/server
/generator
/tests
/registry-library

What does does this PR do / why we need it:

Upgrades the go version for the index/server, index/generator, registry-library & tests/integration from v1.19 to v1.21

Which issue(s) this PR fixes:

Fixes devfile/api#1562

PR acceptance criteria:

  • Test Coverage
    • Are your changes sufficiently tested, and are any applicable test cases added or updated to cover your changes?

Documentation (WIP)

How to test changes / Special notes to the reviewer:

@openshift-ci openshift-ci bot requested review from elsony and Jdubrick May 29, 2024 15:41
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 29, 2024
@thepetk
Copy link
Contributor Author

thepetk commented May 29, 2024

WIP because I'd like to test it with a local deployment of the registry. Not sure if we should vendor the tests/integration dir

@thepetk thepetk changed the title WIP: Upgrade support modules to go1.21 Upgrade support modules to go1.21 May 29, 2024
@thepetk
Copy link
Contributor Author

thepetk commented May 29, 2024

WIP because I'd like to test it with a local deployment of the registry. Not sure if we should vendor the tests/integration dir

Decided not to include vendor files for test/integration. Also tested locally and both viewer & server look working :)

Copy link
Member

@michael-valdron michael-valdron left a comment

Choose a reason for hiding this comment

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

@thepetk
Copy link
Contributor Author

thepetk commented May 31, 2024

Changes to the modules looks good, few change requests:

  1. You'll need to update Go version in the CI workflow files:

  2. You'll need to update the Go version in the Dockerfiles:

Note: In addition to needing the open seperate PR(s) for bumping the devfile/api version (and k8s indirect dependencies) to resolve the issue completely, this also contributes to resolving devfile/api#1557.

Yeah my bad forgot to push my latest changes :( I've also re-created the PR as I needed to rebase a lot of stuff. I think now is completed.

I feel we can include the bump up of the devfile/api in the current PR. We just need to complete devfile/api#1567 I guess and then bump up the version to v2.3.0

@thepetk
Copy link
Contributor Author

thepetk commented May 31, 2024

@michael-valdron a question here is should we go to 2.3.0-alpha instead of 2.3.0?

@thepetk thepetk changed the title Upgrade support modules to go1.21 [DO NOT MERGE] Upgrade support modules to go1.21 May 31, 2024
@thepetk
Copy link
Contributor Author

thepetk commented May 31, 2024

@michael-valdron a question here is should we go to 2.3.0-alpha instead of 2.3.0?

After discussion we'll go with 2.3.0.

FYI I've opened devfile/api#1571 in order to release devfile/api version 2.3.0. Post merge I'll update the current PR for registry-library to use the latest api version.

@thepetk thepetk changed the title [DO NOT MERGE] Upgrade support modules to go1.21 Upgrade support modules to go1.21 Jun 3, 2024
@thepetk
Copy link
Contributor Author

thepetk commented Jun 3, 2024

@michael-valdron a question here is should we go to 2.3.0-alpha instead of 2.3.0?

After discussion we'll go with 2.3.0.

FYI I've opened devfile/api#1571 in order to release devfile/api version 2.3.0. Post merge I'll update the current PR for registry-library to use the latest api version.

@michael-valdron the devfile/api 2.3.0 is now released. I've included the bump up of devfile/api in server and generator in this PR. Once I've fixed the status failures, If I'm not wrong we need a separate PR to update the generator dependency on server & registry-library right?

@thepetk thepetk changed the title Upgrade support modules to go1.21 WIP: Upgrade support modules to go1.21 Jun 4, 2024
@thepetk
Copy link
Contributor Author

thepetk commented Jun 4, 2024

WIP: Because we need to fix the issue brought from code gen and updates the import of the index generator schema:

"sigs.k8s.io/structured-merge-diff/v4/schema"

@michael-valdron
Copy link
Member

@michael-valdron a question here is should we go to 2.3.0-alpha instead of 2.3.0?

After discussion we'll go with 2.3.0.
FYI I've opened devfile/api#1571 in order to release devfile/api version 2.3.0. Post merge I'll update the current PR for registry-library to use the latest api version.

@michael-valdron the devfile/api 2.3.0 is now released. I've included the bump up of devfile/api in server and generator in this PR. Once I've fixed the status failures, If I'm not wrong we need a separate PR to update the generator dependency on server & registry-library right?

@thepetk server should be fine to update now as it references the local generator with replace and builds with it, in the case of registry-library despite the replace it should be updated in a separate PR because it can be shipped by itself and will need the revision updated.

Signed-off-by: thepetk <thepetk@gmail.com>
Signed-off-by: thepetk <thepetk@gmail.com>
Signed-off-by: thepetk <thepetk@gmail.com>
Signed-off-by: thepetk <thepetk@gmail.com>
Signed-off-by: thepetk <thepetk@gmail.com>
Signed-off-by: thepetk <thepetk@gmail.com>
Signed-off-by: thepetk <thepetk@gmail.com>
Signed-off-by: thepetk <thepetk@gmail.com>
Signed-off-by: thepetk <thepetk@gmail.com>
@thepetk thepetk changed the title WIP: Upgrade support modules to go1.21 Upgrade support modules to go1.21 Jun 7, 2024
@thepetk
Copy link
Contributor Author

thepetk commented Jun 7, 2024

I've updated the PR by adding the package in the template inside index/server/config/types.yaml thanks to @michael-valdron

cc @Jdubrick

Signed-off-by: thepetk <thepetk@gmail.com>
Signed-off-by: thepetk <thepetk@gmail.com>
Copy link

codecov bot commented Jun 8, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 41.44%. Comparing base (c1f12da) to head (93dd0ea).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #243   +/-   ##
=======================================
  Coverage   41.44%   41.44%           
=======================================
  Files           9        9           
  Lines        3132     3132           
=======================================
  Hits         1298     1298           
  Misses       1643     1643           
  Partials      191      191           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Contributor

@Jdubrick Jdubrick left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 10, 2024
Copy link
Member

@michael-valdron michael-valdron left a comment

Choose a reason for hiding this comment

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

/lgtm

Copy link

openshift-ci bot commented Jun 10, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Jdubrick, michael-valdron, thepetk

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:
  • OWNERS [Jdubrick,michael-valdron,thepetk]

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

@thepetk thepetk merged commit ee1d190 into devfile:main Jun 10, 2024
10 checks passed
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. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Devfile Registry library module should be updated to support Go 1.21
4 participants