You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This epic will contain a number of issues related to zos_job_query , while some of the issues are bug fixes or issues waiting on dependencies from ZOAU, collectively these issues should address the performance concerns of the module raised in issue #1606 , see comment.
There could be a 4th issue, it is not created because it depends mostly on what issue (1) returns but also how much more performant the module is after bullets 2 and 3. This 4th issue would only be needed when the module gets the program_name from ZOAU and it performs poorly then we would want to offer an option to disable getting it to improve the performance. Since we currently return it, it would make sense to leave that behavior and offer an option to return an empty string (no call to get program_name) making it a users decision to not have it returned.
These two issues are not currently owned by this epic, but are indirectly related:
Is there an existing issue for this?
Enabler description
This epic will contain a number of issues related to
zos_job_query
, while some of the issues are bug fixes or issues waiting on dependencies from ZOAU, collectively these issues should address the performance concerns of the module raised in issue #1606 , see comment.There could be a 4th issue, it is not created because it depends mostly on what issue (1) returns but also how much more performant the module is after bullets 2 and 3. This 4th issue would only be needed when the module gets the
program_name
from ZOAU and it performs poorly then we would want to offer an option to disable getting it to improve the performance. Since we currently return it, it would make sense to leave that behavior and offer an option to return an empty string (no call to get program_name) making it a users decision to not have it returned.These two issues are not currently owned by this epic, but are indirectly related:
Ansible module
No response
The text was updated successfully, but these errors were encountered: