qvm-ls --raw-data: also remove the []{}=> chars

[rootkovska]

Just make it easier to write bash scripts, avoid piping through additional tr -d :)

[jpouellet]

I am currently relying on this in one of my scripts, and using --raw-list where plain names are desired. I'm more than happy to change my parsing as I think it would actually simplify things anyway, but one question I even had at the time was what Qubes interfaces should be considered stable? This would be nice to have an actual documented policy on.

As for the specifics of this case, I can easily change it to check ip back != n/a instead of {}, and type = Tpl instead of [].

That leaves only =>. What do you suggest is the best way to expose that? Additional field hidden from default view?

[jpouellet]

I am currently relying on this in one of my scripts, and using --raw-list where plain names are desired. I'm more than happy to change my parsing as I think it would actually simplify things anyway, but one question I even had at the time was what Qubes interfaces should be considered stable? This would be nice to have an actual documented policy on.

As for the specifics of this case, I can easily change it to check ip back != n/a instead of {}, and type = Tpl instead of [].

That leaves only =>. What do you suggest is the best way to expose that? Additional field hidden from default view?

[jpouellet]

FWIW, core3 looks like the stable interface I actually want.

[jpouellet]

FWIW, core3 looks like the stable interface I actually want.

[marmarek]

That leaves only =>. What do you suggest is the best way to expose that? Additional field hidden from default view?

See qubes-prefs.

FWIW, core3 looks like the stable interface I actually want.

The ugliness of the current interface (and the code behind it) is one of the reason for core3...

@rootkovska does --raw-list solve your case? Otherwise I think we may introduce new field like raw_name to not break compatibility.

[marmarek]

That leaves only =>. What do you suggest is the best way to expose that? Additional field hidden from default view?

See qubes-prefs.

FWIW, core3 looks like the stable interface I actually want.

The ugliness of the current interface (and the code behind it) is one of the reason for core3...

@rootkovska does --raw-list solve your case? Otherwise I think we may introduce new field like raw_name to not break compatibility.

[jpouellet]

There is also <dispN>

[jpouellet]

There is also <dispN>