-
Notifications
You must be signed in to change notification settings - Fork 53
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
Build images with cockpit (HMS-5417) #2787
Build images with cockpit (HMS-5417) #2787
Conversation
253559b
to
d2479f6
Compare
df3f978
to
979eb42
Compare
Codecov ReportAttention: Patch coverage is
@@ Coverage Diff @@
## main #2787 +/- ##
==========================================
- Coverage 84.55% 83.22% -1.33%
==========================================
Files 190 190
Lines 21811 22214 +403
Branches 2169 2174 +5
==========================================
+ Hits 18442 18488 +46
- Misses 3347 3704 +357
Partials 22 22
Continue to review full report in Codecov by Sentry.
|
979eb42
to
e417e88
Compare
e417e88
to
929c498
Compare
929c498
to
01f12b6
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.
Great stuff. Just had some comments about the tags stuff that could be added to the enhancedCockpitApi
instead but pretty minor.
Edit to add: this should probably clear up the type errors too
d605846
to
32be84b
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.
LGTM, think the PR just needs a description :)
/jira-epic COMPOSER-2411 |
`.cache` is for writing, `.local/share` is technically static data.
The structure of the local cache is now: ``` └── blueprint └── blueprint.json └── image1 └── image2 └── blueprint2 └── blueprint2.json └── image1 ``` Building an image reads the blueprint, and creates a new image file under the relevant blueprint folder, which contains the image request. The image request that's sent off to composer and the request that's saved differs slightly in the upload structures.
The mixed api supports both the service and on-prem.
Reads all of the image entries under the cache.
Finds the relevant compose, asks for its status and reads the original compose request from disk.
Adds `mtime` tot fsinfo, and `replace` to `cockpit.file`.
With the custom query functions the cached data from getComposes and getBlueprintComposes doesn't get invalidated. Luckily RTKQuery provides a mechanism to invalidate the cache after a mutation.
32be84b
to
df0fbcc
Compare
cockpit-ib.mp4
JIRA: HMS-5417