-
Notifications
You must be signed in to change notification settings - Fork 143
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
k8s_cp turbo mode compliance #254
k8s_cp turbo mode compliance #254
Conversation
72d4b6c
to
d72e82f
Compare
Build failed.
|
Build succeeded.
|
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.
Am I wrong or the check_mode logic is not handled here (even if the module has supports_check_mode=True)?
check_mode is not supported by the module even if it states that, but this should be addressed in another PR |
So, I was just wondering if it would be better to have it set to False if it's not supported. @gravesm |
That's fine. Please, create an issue for it. |
Build failed.
|
recheck |
Build succeeded.
|
@alinabuzachis @gravesm the build succeeded and #380 has been created to track support for check_mode. |
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. Thanks!
regate |
7e0faf3
to
c32b9d6
Compare
regate |
recheck |
Build succeeded.
|
regate |
This ports commit 44c8cff to the refactored code.
SUMMARY
closes #237
ISSUE TYPE
COMPONENT NAME
ADDITIONAL INFORMATION