updates post vmware_rest release 4.0.0 #89
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mikemorency
force-pushed
the
mm-feature/vmware-rest-release-4
branch
from
8a01a23 to
e7781c0
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SUMMARY
These are changes I had to make to succesfully generate content in vmware.vmware_rest release 4.0.0. It included a new openapi spec, which introduced some new data types (corresponding to existing or new modules).
Additionally, i had to update the asyncio initialization for python 3.12. The previous was of getting a loop has been deprecated. The method included in this PR passed python 3.8 + sanity checks
ISSUE TYPE
COMPONENT NAME
generate_cloud_modules
vmware_rest
ADDITIONAL INFORMATION
Related: ansible-collections/vmware.vmware_rest#511