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.

Sign up for GitHub

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

Jump to bottom

Implicitly extract tar.gz files from plugins that upload them #47

Merged
merged 1 commit into from
Aug 10, 2017
Merged

Implicitly extract tar.gz files from plugins that upload them #47

merged 1 commit into from
Aug 10, 2017

Commits on Aug 10, 2017

  1. Implicitly extract tar.gz files from plugins that upload them 

    This makes it so plugins upload to a path like:

```
/api/v1/results/global/e2e.tar.gz
```

And it will show up in:

```
/results/plugins/e2e/results/<contents>
```

(For single-node plugins, this would map to:)

```
/results/plugins/systemd_logs/node1/<contents>
```

This needs to be documented along with the snapshot documentation that
is already under review.

Since the upload path is now expected to have a file extension in it, In
case for some reason the sonobuoy master launches with an old version
of the sonobuoy worker (or for plugins not using `sonobuoy worker` that
upload their own contents), if the path has no file extension, it is
guessed to be `.json` or `.tar.gz`, same as before.

Signed-off-by: Ken Simon <[email protected]>
    Ken Simon committed Aug 10, 2017
    Configuration menu
    Copy the full SHA
    5082fc2 View commit details
    Browse the repository at this point in the history