-
Notifications
You must be signed in to change notification settings - Fork 205
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
mini update 7: describe push workflow #167
Conversation
Signed-off-by: Peter Engelbert <[email protected]>
f714b79
to
dafe1e1
Compare
The various flavors of Push I would imagine are related to the various client constraints one may have. For example, when memory constrained, when network is flaky (so need frequent resuming), when there are no real constrains (so I can push in one shot), etc. Clients today for whatever reason have decided to implement only a single flavor. |
This is a new table of contents for the spec, designed to add simplicity and organization. Existing content will later be moved into one of these sections, or removed entirely if considered superfluous. Signed-off-by: jdolitsky <[email protected]>
Signed-off-by: jdolitsky <[email protected]>
Fill in the overview section, including new introduction referring to "content" (vs. just container images). Move historical context section underneath overview. Signed-off-by: jdolitsky <[email protected]>
Fill in the definitions section, introducing several terms and defintions which will serve as reference for the rest of the document. Also moved the "notational conventions" section into this section, removing any language that seemed unnecessary or related to compliance (which will be covered in the conformance section). Signed-off-by: jdolitsky <[email protected]>
Signed-off-by: jdolitsky <[email protected]>
Fill in conformance section, adding minimum requirements stating that all compliant registries must at least support Pull. Added a section regarding certification, linking to the opencontainers/oci-conformance repo. For the workflow sections, intentionally left blank, and will be added in a follow-up PR. Signed-off-by: jdolitsky <[email protected]>
Fill in conformance section, adding minimum requirements stating that all compliant registries must at least support Pull. Added a section regarding certification, linking to the opencontainers/oci-conformance repo. For the workflow sections, intentionally left blank, and will be added in a follow-up PR. Signed-off-by: jdolitsky <[email protected]>
Signed-off-by: Peter Engelbert <[email protected]>
…-spec into mini-update-6 Signed-off-by: Peter Engelbert <[email protected]>
…-spec into mini-update-6 Signed-off-by: Peter Engelbert <[email protected]>
dafe1e1
to
8e13311
Compare
…-spec into mini-update-6 Signed-off-by: jdolitsky <[email protected]>
8e13311
to
b347ee5
Compare
<manifest byte stream> | ||
``` | ||
|
||
`<name>` is the namespace of the repository, and the `<reference>` MUST be either a) a digest or b) a tag. |
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.
nothing actionable in this PR, but tag should be added to definitions
Signed-off-by: Peter Engelbert <[email protected]>
Signed-off-by: Peter Engelbert <[email protected]>
Signed-off-by: Peter Engelbert <[email protected]>
b347ee5
to
d44db2d
Compare
Closing this in favor of #178 |
Builds on PR #166
The relevant diff can be found here:
https://github.com/bloodorangeio/distribution-spec/compare/mini-update-6...bloodorangeio:mini-update-7?expand=1
This is a larger section and will need review before finalization--thank you for your comments.