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

CLI tooling to inspect bundles #3754

Closed
tsandall opened this issue Aug 19, 2021 · 5 comments
Closed

CLI tooling to inspect bundles #3754

tsandall opened this issue Aug 19, 2021 · 5 comments

Comments

@tsandall
Copy link
Member

tsandall commented Aug 19, 2021

Bundles are pretty simple. We can summarize their structure and contents as follows:

  • They are gzipped tarballs
  • They can contain .rego files in any location
  • They can contain data.json and data.yaml files that are mounted into data based on their directory path
  • They can contain a .manifest file with various metadata bits
  • They can contain policy.wasm files that are mounted into data based on "resolver" configuration in the manifest
  • They can contain a signatures.json file with cryptographic signatures on the files above

At 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 in opa 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 the data locations defined by the data.json, etc. files.

It could also be nice to have the tooling support comparisons on bundles.

@ipapast
Copy link

ipapast commented Sep 26, 2021

Hey, Is there a rough timeline for this work in progress?

@ashutosh-narkar
Copy link
Member

This task is actively being worked on. It should land in the next couple of releases.

@ipapast
Copy link

ipapast commented Oct 20, 2021

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?

@anderseknert
Copy link
Member

@ipapast we try to follow a monthly release cadence, with a new release expected by the end of each month.

@anderseknert
Copy link
Member

Done in #3830

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

4 participants