The main goal of this change is to advance the supported VCF version for the provider to the latest release.
The new API definitions contain several type and method name changes as well as some changes to optional parameters.
Please review the list of commits for a detailed picture of each change included in this PR.
5.1.1 is a significant jump from 4.5.2
This change only aims to make the provider officially compatible with 5.1.1
It does not introduce any new resources, properties and does not in any way change the current interface of the provider.
Type of Pull Request
[ ] This is a bug fix.
[ ] This is an enhancement or feature.
[ ] This is a code style/formatting update.
[ ] This is a documentation update.
[ ] This is a refactoring update.
[X] This is a chore update
[ ] This is something else.
Please describe:
Related to Existing Issues
Issue Number: N/A
Test and Documentation Coverage
I ran at least 1 acceptance test per resource/data source. In the cases where there are multiple tests I only ran the most comprehensive one.
Summary of Pull Request
The main goal of this change is to advance the supported VCF version for the provider to the latest release. The new API definitions contain several type and method name changes as well as some changes to optional parameters.
Please review the list of commits for a detailed picture of each change included in this PR.
5.1.1 is a significant jump from 4.5.2 This change only aims to make the provider officially compatible with 5.1.1 It does not introduce any new resources, properties and does not in any way change the current interface of the provider.
Type of Pull Request
Related to Existing Issues
Issue Number: N/A
Test and Documentation Coverage
I ran at least 1 acceptance test per resource/data source. In the cases where there are multiple tests I only ran the most comprehensive one.
For bug fixes or features:
Breaking Changes?