oras--verbose flag instead of removing it for commands that don't support it? https://github.com/oras-project/oras/issues/1640 (Sylvia Lei)--verbose flag available in 6 oras commands but remain deprecation warning message in the output. This flag will be entirely removed in oras v2.0 considering this is a breaking change.Recording: https://youtu.be/3HYgugHD0fQ
oras.land. @sabre1041 will help Valentine to create a service ticket to request CNCF's help on getting the group id for the domain https://github.com/oras-project/oras-java/pull/100referrers as the field name in the top-level and second-level referrers, instead of manifests--depth to allow users to limit the maximum depth of referrers in the formatted output.--format tree-full https://github.com/oras-project/oras/pull/1602 (Terry & Feynman)--format tree-fullorg.opencontainers.image.ref.name contains a full referenceorg.opencontainers.image.ref.name contains a full reference. @Feynman will also tag the issue author to provide his feedback on 3 proposals from @shizh and Terry.oras-go repo? https://github.com/oras-project/oras-go/issues/828oras-go repo. Sylvia will raise a PR to implement it.We discussed these questions regarding the PR docs: Improve ORAS diagnose experience and reached consensus as follows:
--verbose and remain --debug as it is?
--verbose and remain --debug as a unified control of debug logs. The original output of --verbose will be reserved in several oras commands pull/push/attach/discover by introducing an additional flag. The major reason is that the --debug option is more consistent with the other popular client tools and also to avoid overloading --verboseexport ORAS_DEBUG=1 as a global switch for debug logs? What are the Pros and Cons of using this design?
--debug is intuitive enough.oras version rather than in debug logs? The details about the environment where the tool is running, such as OS version and architecture, tool version, and environment variables (excluding sensitive data) would be super helpful to help ORAS developers and users to diagnose an issue.
OS/Arch to the default output of oras version. It is hard to capture the distribution name and version, and they are not always available.--debug, should ORAS applies other log levels like INFO, ERROR, WARNING to differentiate the debug log information?
--debug.Recording: Video recording is published on Youtube and Zoom chat message is available here
Skipped due to no agenda collected from the community
We skipped this meeting since no topics collected and several ORAS maintainers are on vacation.
oras loginRecording: https://www.youtube.com/live/2iiOc8JjUOw?si=sYOv6jBWwF4L40h5
oras-go v2.5.0
image-spec v1.1.0 and distribution-spec v1.1.0Recording: https://youtube.com/live/ps5i5JPwV-4
Skipped due to no agenda and attendees
Meeting recording: https://youtu.be/sRv6ZTus5gk
TBD
oras-go? (Sylvia)
Video: https://www.youtube.com/watch?v=9Mc_ZChp4gc
TBD
TBD
(template for copying)
-
Any changes
Be notified of any changes
-
Mention me
Be notified of mention me
-
Unsubscribe
Subscribe