-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Remove k8s_status module, install from galaxy #2310
Remove k8s_status module, install from galaxy #2310
Conversation
097da81
to
dab5a87
Compare
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
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.
Just the @estroz nits
And then, /lgtm /approved for me as well 🥇
New changes are detected. LGTM label has been removed. |
fad0802
to
3eb0c27
Compare
Co-Authored-By: Eric Stroczynski <estroczy@redhat.com>
3eb0c27
to
f1d15fb
Compare
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, after addressing my one nit/question.
collections: | ||
- operator_sdk.util` |
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.
Is there a best practice between declaring the collection like this and then using the shortened name in tasks vs using the fully qualified name in tasks?
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.
They don't seem to have a preference yet.
https://docs.ansible.com/ansible/devel/user_guide/collections_using.html#using-collections-in-a-playbook
No description provided.