-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
CLI tooling to inspect bundles #3754
Comments
Hey, Is there a rough timeline for this work in progress? |
This task is actively being worked on. It should land in the next couple of releases. |
hey @ashutosh-narkar and @tsandall I can see this is merged but not released, thanks so much for this. is it possible to give me an ETA for the next release? |
@ipapast we try to follow a monthly release cadence, with a new release expected by the end of each month. |
Done in #3830 |
Bundles are pretty simple. We can summarize their structure and contents as follows:
data
based on their directory pathdata
based on "resolver" configuration in the manifestAt the same time, to inspect them, users have to run various unix commands like
tar
,cat
,ls
, etc. It would be nice to have a subcommand inopa
that could print a description of the bundle for debugging purposes. Specifically, it be nice to see a summary of the packages that are contributed by .rego files in bundle as well as thedata
locations defined by the data.json, etc. files.It could also be nice to have the tooling support comparisons on bundles.
The text was updated successfully, but these errors were encountered: