-
Notifications
You must be signed in to change notification settings - Fork 64
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
New release #332
Comments
Hi @mariolenz, I'm not sure if the request is for community.vmware or vmware.vmware_rest. |
@goneri Ah, sorry! I think I have a C&P failure there! |
@goneri Is there a chance to see a 2.1.6 or 2.2.0 release of |
I think it's already too late to get a current release of this collection into Ansible 6.0.0 😢 |
SUMMARY
We are running sanity tests across every collection included in the Ansible community package (as part of this issue).
I hope I've fixed all remaining problems in #331. However, since we're testing against the release that's part of the Ansible community package, and those fixes aren't part of a release yet, I think we'll run into failing tests once
community.vmware
vmware.vmware_rest
is added.In order to avoid this, it would be really great if you could release a new version of this collection in time for Ansible 6.0.0a3 (Tuesday or Wednesday next week, I think).
cc @goneri @dmsimard
ISSUE TYPE
COMPONENT NAME
n/a
ADDITIONAL INFORMATION
The text was updated successfully, but these errors were encountered: