-
Notifications
You must be signed in to change notification settings - Fork 44
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
[v1.10.0] [Enabler] Standardization of choices in modules #1388
Conversation
This also includes major work on zos_data_set since half of the test suite for zos_archive depends on creating data sets.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is an amazing piece of work! Very detailed. I have found 2 issues which may need changing, or I may misunderstand what I saw. Let me know either way.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't have any question that is not currently asked by Rich.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM- amazing work here Ivan!! Thanks for delivering this mighty effort (which was merely an idea just last week)!!
I've also validated the functionality delivered here while updating (and running) the playbooks in the samples repo.
I think there are some places where stylistic changes could be made, eg:
- instead of removing a call to
upper()
, replace it with a call tolower()
- leaving params in lower-case until upper is required (eg for certain zoau calls)
But, we should make those as part of other development efforts rather than here. The interface has been updated and I saw no gaps in functionality, so I'd consider this issue completed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the explanations. I wanted to be sure the remaining capitalization was intentional. Nice work!
SUMMARY
Fixes #1360
ISSUE TYPE
COMPONENT NAME
ibm_zos_core
ADDITIONAL INFORMATION