Skip to content
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

Pull in latest go-vcloud-director SDK with 10.1 fixes #489

Merged
merged 18 commits into from
Apr 10, 2020

Conversation

Didainius
Copy link
Collaborator

@Didainius Didainius commented Apr 7, 2020

This PR just bumps go-vcloud-director SDK to the latest one so that 10.1 related fixes are in place.
It also covers the following:

@Didainius Didainius self-assigned this Apr 7, 2020
Copy link
Collaborator

@lvirbalas lvirbalas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you! Let's get this in!

Copy link
Contributor

@dataclouder dataclouder left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ghost ghost added size/L documentation and removed size/M labels Apr 9, 2020
@Didainius Didainius merged commit b1ef030 into vmware:master Apr 10, 2020
@Didainius Didainius deleted the test-pvdc-nsxt-fix branch April 10, 2020 07:56
Didainius added a commit that referenced this pull request Apr 15, 2020
* Add vCD 10.1 vcd_org_vdc fix note to changelog which was actually fixed with #489 by pulling in go-vcloud-director SDK version vmware/go-vcloud-director#293
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

vApp may need powering off to avoid vApp network removal errors
4 participants