-
Notifications
You must be signed in to change notification settings - Fork 165
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
Add S3 metadata in meta.json #2731
Conversation
Let's mark this as Draft, as I think there is some more design to be discussed here. |
I think the primary question is how do we want to encode information that is specific to the build pipeline into meta.json? Perhaps a new function that we can call during the pipeline execution to write the specific values from the pipeline? |
We can add some arg for |
That sounds good to me! Let's keep this in Draft to see if other folks have input. Could you also edit the first comment to give a bit more rationale for the change and why we want it? |
👍 That would be welcome. I'm assuming this is related to GC, correct? It sounds like you already have a design in mind. Would be good to write it up somewhere where we can discuss it (maybe a new issue on this repo?). |
It's more about providing information about the source of truth for RHCOS builds see - https://issues.redhat.com/browse/COS-1224 |
Opened an issue for wider discussion - #2739 |
2c3060f
to
29accc9
Compare
f95592c
to
2b48f39
Compare
250df18
to
c69f5fe
Compare
9e6e6f1
to
56de10b
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.
one small change requested, but otherwise i think this looks ready!
is there an example |
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.
This LGTM overall! Just wanted to make sure also that you saw #2731 (comment) and #2731 (comment).
24c25aa
to
55baa72
Compare
Yeah, totally missed these. Thanks for all the review @jlebon |
help='Store key information in meta.json') | ||
|
||
upload_cmd.add_argument( | ||
'--s3-url', required=False, |
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.
Now, it's missing @miabbott's feedback in https://github.com/coreos/coreos-assembler/pull/2731/files#r834404028 :)
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.
Should we change the parameter name to public-url too? I was thinking in let it as url. And only use the public-url structure .
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 think it'd be good to be consistent, but personally fine with it. I'm not really concerned about cosa koji-upload
becoming some API that people outside the CoreOS team starts using.
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'd prefer it to be consistent, but won't block merging on it for the same reasons Jonathan says. :)
- Add S3 metadata in meta.json Signed-off-by: Renata Ravanelli <rravanel@redhat.com>
- Update generate-schema to reflex changes done in golang binaries and directory tree Signed-off-by: Renata Ravanelli <rravanel@redhat.com>
d044f20
to
4e6e43f
Compare
- This change is needed due brew/compliance improvements where we need to keep more information about where the artifacts are archived; - Add s3 parameters in order to update meta.json with bucket, prefix and url information used in S3 upload. Signed-off-by: Renata Ravanelli <rravanel@redhat.com>
help='Store key information in meta.json') | ||
|
||
upload_cmd.add_argument( | ||
'--s3-url', required=False, |
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 think it'd be good to be consistent, but personally fine with it. I'm not really concerned about cosa koji-upload
becoming some API that people outside the CoreOS team starts using.
/retest-required |
No description provided.