-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
[V3] (Part 1) Refactor schema "latest" to "latest/v1" #5728
[V3] (Part 1) Refactor schema "latest" to "latest/v1" #5728
Conversation
@loosebazooka @chanseokoh Please skip reviewing the PR (somehow I can't remove the auto-selected reviewers). we have some previous discussions about this refactoring. @tejal29 and @marlon-gamez have more context. |
f490e92
to
1b08ed5
Compare
Codecov Report
@@ Coverage Diff @@
## master #5728 +/- ##
==========================================
- Coverage 70.88% 70.85% -0.04%
==========================================
Files 421 421
Lines 16087 16087
==========================================
- Hits 11404 11399 -5
- Misses 3849 3851 +2
- Partials 834 837 +3
Continue to review full report at Codecov.
|
1b08ed5
to
3a0e3ec
Compare
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.
I assume the main point of this change is so that we can use latest_v1
and latest_v2
alongside each other right? could you maybe give a hypothetical example of how this might look just to help clarify the motivation for this?
also, would we want a plan for formally deprecating the old config style? or will we want to keep it around indefinitely?
Please visit http://35.236.9.12:1313 to view changes to the docs. |
@nkubala Yeah, you can find the motivations, examples and the year-long deprecation in this code-refactoring doc "Versioning the latest package" section (attached in issue #5727) |
1e82bc3
to
ca8cafb
Compare
Rebased to head and fixed merging conflict. |
a3ac4e8
to
ce15b78
Compare
See details in [doc](https://docs.google.com/document/d/1GFy_5ya-ajjSVe1t6f7IWUlAQu35eTHAZZ1GkJBiqcA/edit?resourcekey=0-sKE-yXjuymQ0w2qqNXnTzw#heading=h.az97ji6gorca) - In pkg/skaffold/schema, move ./latest/* to ./latest/v1/* (so as later on once we add v2, v1 and v2 can both be imported as latest) - Update the reference of "latest" to "latest_v1" (pkg/ cmd/ integration/) - Fix build.ArtifactDependencies reference in pkg/build/maven. Note: We use alias `latest_v1` instead of `v1` to import package pkg/skaffold/schema/latest/v1. The "latest" prefix is to distinguish another "v1" package which is also under pkg/skaffold/schema Next: some latest_v1 reference may be bisected for v2 package.
ce15b78
to
bfccb7c
Compare
yeah I think @briandealwis saw this too and opened an issue #5733 The |
I restarted the test and will merge after |
Related: #5727
Description
Note: We use alias
latest_v1
instead ofv1
to import package pkg/skaffold/schema/latest/v1.The "latest" prefix is to distinguish another "v1" package which is also under pkg/skaffold/schema
Follow-up Work
To reviewers
the main change is about the new directory
pkg/skaffold/schema/latest/v1
, whoseconfig.go
andupgrade.go
are frompkg/skaffold/schema/latest
. The other 240+ files are just updating the package import to "latest/v1".