vRA8 requires the domain attribute set when creating the VM, instead of the older tenant attribute. Today, the kitchen-vra gem passes the domain via the tenant attribute in the kitchen.yml file. This confuses users. This PR is to introduce a domain attribute (mark it required) and deprecate the existing tenant attribute.
The user needs to define the domain rather than the tenant in the kitchen.yml file when using the kitchen-vra plugin on the vRA8 setup.
The API Wrapper gem(vmware-vra) is updated with the same attribute change and a new version 3.2.0 is released. Updated the dependency of this gem to install vmware-vra >= 3.2.0.
Issues Resolved
List any existing issues this PR resolves, or any Discourse or
StackOverflow discussions that are relevant
Signed-off-by: Ashique P S Ashique.saidalavi@progress.com
Description
vRA8 requires the domain attribute set when creating the VM, instead of the older tenant attribute. Today, the kitchen-vra gem passes the domain via the tenant attribute in the kitchen.yml file. This confuses users. This PR is to introduce a domain attribute (mark it required) and deprecate the existing tenant attribute.
The user needs to define the domain rather than the tenant in the kitchen.yml file when using the
kitchen-vraplugin on the vRA8 setup.The API Wrapper gem(vmware-vra) is updated with the same attribute change and a new version
3.2.0is released. Updated the dependency of this gem to installvmware-vra >= 3.2.0.Issues Resolved
List any existing issues this PR resolves, or any Discourse or StackOverflow discussions that are relevant
Type of Change
Our release process assumes you are using Conventional Commit messages.
The most important prefixes you should have in mind are:
_fix_: which represents bug fixes, and correlates to a SemVer patch._feat_: which represents a new feature, and correlates to a SemVer minor._feat!_:, orfix!:,refactor!:, etc., which represent a breaking change (indicated by the !) and will result in a major version change.If you have not included a conventional commit message this can be fixed on merge.
Check List