-
Notifications
You must be signed in to change notification settings - Fork 57
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
Prep vmware.vmware_rest 3.0.0 #450
Prep vmware.vmware_rest 3.0.0 #450
Conversation
Signed-off-by: Alina Buzachis <abuzachis@redhat.com>
Signed-off-by: Alina Buzachis <abuzachis@redhat.com>
Signed-off-by: Alina Buzachis <abuzachis@redhat.com>
@alinabuzachis The modules still say "Tested on vSphere 7.0.2", but I think the CI is running 7.0.3 (vSphere 7.0 U3). I'm not 100% sure, maybe @jillr can say something about the actual version. If so, should this be changed to "Tested on vSphere 7.0.3"? Of course, we would have to do it in ansible.content_builder here. Maybe this should be configurable in the MANIFEST.yaml (and also the vSphere requirements?) so the content_builder doesn't have to be changed for this. |
Build failed.
|
I guess you are right. @mariolenz |
And I also think "Tested on vSphere 7.0.2" should be updated to "Tested on vSphere 7.0.3" in the content builder. Same for the vsphere requirements. I'm not sure if these can be set in the MANIFEST.yaml file. It will probably be easy for the moment to open a PR to update the content builder (just to speedup the vmware_rest release) and then try to see how this can be set in the MANIFEST file directly. |
I'll open one, no problem. |
Superseded by #451 |
SUMMARY
Prep vmware.vmware_rest 3.0.0
ISSUE TYPE
COMPONENT NAME
several