Skip to content
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

Offline use documentation includes obsolete flag to oras #2580

Closed
hlein opened this issue Jul 25, 2022 · 2 comments · Fixed by #2582
Closed

Offline use documentation includes obsolete flag to oras #2580

hlein opened this issue Jul 25, 2022 · 2 comments · Fixed by #2582
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@hlein
Copy link

hlein commented Jul 25, 2022

Description

The documentation for air-gapped/offline use (https://aquasecurity.github.io/trivy/v0.30.2/docs/advanced/air-gap/) says to use oras to fetch like so:

$ oras pull ghcr.io/aquasecurity/trivy-db:2 -a

However, current oras throws a usage message:

$ oras pull ghcr.io/aquasecurity/trivy-db:2 -a                                                                    
Error: unknown shorthand flag: 'a' in -a
$ oras version
Version:        0.13.0+unreleased
Go version:     go1.18.4
Git tree state: clean

Per oras-project/oras#130 and oras-project/oras#387, -a/--allow-all behavior is now the default, and those arguments have been removed, apparently with no deprecated-warning grace period.

@hlein hlein added the kind/bug Categorizes issue or PR as related to a bug. label Jul 25, 2022
@DmitriyLewen
Copy link
Contributor

Hello @hlein
Thanks a lot for your report!

We will update information about this in the docs.

Best Regards, Dmitriy

@hlein
Copy link
Author

hlein commented Jul 27, 2022

We will update information about this in the docs.

Sweet, thanks for the quick fix @DmitriyLewen !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants