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 use machine automation friendly output #38290

Closed
dragon788 opened this issue Dec 15, 2016 · 6 comments
Closed

Need to use machine automation friendly output #38290

dragon788 opened this issue Dec 15, 2016 · 6 comments
Labels
Bug broken, incorrect, or confusing behavior Execution-Module P4 Priority 4 Platform Relates to OS, containers, platform-based utilities like FS, system based apps severity-low 4th level, cosemtic problems, work around exists Windows
Milestone

Comments

@dragon788
Copy link
Contributor

Using Salt 2016.3.3

I've just been testing a bit with the salt.modules.chocolatey and I discovered an issue with the chocolatey list --local-only calls. Calling salt * chocolatey.list local_only=True was returning extra data. It needs the --limit-output argument added to the --local-only so that it doesn't print the "XX packages installed" or the "Chocolatey v0.10.3", both of which gets parsed into the data returned as packages: - XX and Chocolatey: - v0.10.3 while the rest of the packages have a strictly SemVer compatible version.

I'll open a PR to at least fix the calls to choco list, but using the --limit-output should return data structures for almost all choco calls which should make wrapping them easier.

@Ch3LL
Copy link
Contributor

Ch3LL commented Dec 15, 2016

@dragon788 thanks for bringin our attention to this. Look forward to the PR :)

@Ch3LL Ch3LL added Bug broken, incorrect, or confusing behavior Execution-Module severity-low 4th level, cosemtic problems, work around exists P4 Priority 4 Platform Relates to OS, containers, platform-based utilities like FS, system based apps Windows labels Dec 15, 2016
@Ch3LL Ch3LL added this to the Approved milestone Dec 15, 2016
dragon788 added a commit to dragon788/salt that referenced this issue Dec 15, 2016
@dragon788
Copy link
Contributor Author

Looks like I found the states file but not the one in modules which is structured slightly differently. Going to see if I can get a working fix for that one (which seems to be the origin of my issue).

dragon788 added a commit to dragon788/salt that referenced this issue Dec 15, 2016
This actually fixes the issue in saltstack#38290 while the other change should improve the output for the states.
@dragon788
Copy link
Contributor Author

I'll have to test the states.chocolatey functionality, but the modules return data looks better already.

@dragon788
Copy link
Contributor Author

Getting a state failure but no return, not sure if it is related to my changes or the package, will continue investigating tomorrow.

@dragon788
Copy link
Contributor Author

dragon788 commented Dec 16, 2016 via email

dragon788 added a commit to dragon788/salt that referenced this issue Dec 16, 2016
dragon788 added a commit to dragon788/salt that referenced this issue Dec 16, 2016
This actually fixes the issue in saltstack#38290 while the other change should improve the output for the states.
@cachedout
Copy link
Contributor

Closed via #38313

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug broken, incorrect, or confusing behavior Execution-Module P4 Priority 4 Platform Relates to OS, containers, platform-based utilities like FS, system based apps severity-low 4th level, cosemtic problems, work around exists Windows
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants