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

Change how results of mq commands are handled in the queue_manager module #104

Closed
stewmcl opened this issue Apr 24, 2024 · 1 comment
Closed

Change how results of mq commands are handled in the queue_manager module #104

stewmcl opened this issue Apr 24, 2024 · 1 comment
Assignees
@stewmcl
Labels
duplicate This issue or pull request already exists

Comments

@stewmcl
Copy link
Contributor

stewmcl commented Apr 24, 2024 •
edited

Following on from Issue #99

instead of overwriting the results for each queue manager in a list, the result dict should potentially be stored in another dict with the queue manager names being used as the key for each set of results.

These results should then be returned and outputted to the user.
@stewmcl stewmcl added the enhancement New feature or request label Apr 24, 2024
@stewmcl stewmcl self-assigned this Apr 24, 2024
stewmcl added a commit that referenced this issue Apr 25, 2024
@stewmcl
Fix multi queue manager not being set to correct state (#100)
1ae6ab6 
* Changing how the module handles rc's

* Removing unecessary module.exit_json calls

* Removing redundent code


Opened a new issue #104 to handle multiple results that are generated, however these changes being merged in should fix the current problem of not all operations being performed on multiple qm's
@JamRamPage JamRamPage mentioned this issue Apr 25, 2024
Open
@stewmcl stewmcl added duplicate This issue or pull request already exists and removed enhancement New feature or request labels Apr 25, 2024
@stewmcl
Copy link
Contributor Author

stewmcl commented Apr 25, 2024

Closing as a duplicate of #57

@stewmcl stewmcl closed this as not planned Won't fix, can't repro, duplicate, stale Apr 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@stewmcl stewmcl

Labels
duplicate This issue or pull request already exists
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@stewmcl