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

Need to wrap column values in the Table format of subscription list-filters #1052

Open
FarmerMike252 opened this issue Sep 30, 2021 · 3 comments

Comments

@FarmerMike252
Copy link

This may also be true on other table format commands in the subscription manager. I've only done this on list-filters. The main problem is the query is not wrapped.

@FarmerMike252
Copy link
Author

Here is an example of the table formatting (of just one row):
Indication Filters: submgr-id=defaultpywbemcliSubMgr, svr-id=http://FakedUrl:5988 type=all
+-------------+-------------------------------------------+-------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------+---------------------+----------------+
| Ownership | identity | Name | Query | Query | Source | Subscription |
| | | | | Language | Namespaces | Count |
|-------------+-------------------------------------------+-------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------+---------------------+----------------|
| permanent | System Creation | System Creation | SELECT * FROM CIM_InstCreation WHERE SourceInstance ISA CIM_ComputerSystem | | i, n, t, e, r, o, p | 0 |

@KSchopmeyer
Copy link
Contributor

KSchopmeyer commented Oct 1, 2021

Issue in working branch of feature pr #987. Note that this occurs in windows but not linux.

@KSchopmeyer
Copy link
Contributor

Agreed that the wrapping is not optimum. Since this is in a working branch, we can correct in that branch,

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