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

Listing of releases should output dataset #708

Closed
urosgruber opened this issue Apr 7, 2019 · 4 comments
Closed

Listing of releases should output dataset #708

urosgruber opened this issue Apr 7, 2019 · 4 comments

Comments

@urosgruber
Copy link
Contributor

I think it would be nice to show dataset as well. Looks kinda confusing right now

ioc list -r

+--------------+
|  FULL_NAME   |
+==============+
| 11.2-RELEASE |
+--------------+
| 12.0-RELEASE |
+--------------+
| 11.2-RELEASE |
+--------------+
| 12.0-RELEASE |
+--------------+
@gronke
Copy link
Member

gronke commented Apr 8, 2019

For jails, libioc prints full identifiers (<SOURCE_DATASET_NAME>/<JAIL_NAME>) as soon as there is more than one dataset configured. The same should happen for release names.

@urosgruber
Copy link
Contributor Author

Weird. I have two datasets and each have both releases. But there is not details of dataset and in case I would have some other release only on one of them I wouldn't know to what dataset release belongs.

@gronke
Copy link
Member

gronke commented Apr 8, 2019

Weird. I have two datasets and each have both releases.

They are necessary to clone new jails from. Cloning across pools might not be possible, so libioc requires to have each release available on all source datasets.

But there is not details of dataset and in case I would have some other release only on one of them I wouldn't know to what dataset release belongs.

Understood. The issue here is that ioc list -r does not support output columns. This is an issue of the CLI. (see bsdci/ioc#30)

@urosgruber
Copy link
Contributor Author

I guess this one can be closed then.

@igalic igalic closed this as completed Apr 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants