feat(tart provider): Consolidate VM name logic and add vendor to .gitignore #523
+18
−0
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.
This PR implements support for the tart provider in kitchen-vagrant by consolidating the VM name setting logic, addressing the review feedback from PR #503.
Changes Made
case config[:provider]blocks into a single one for settingp.nameintemplates/Vagrantfile.erb, improving code maintainabilitykitchen-<root>-<instance>instead ofkitchen-<root>-<instance>-<uuid>)spec/kitchen/driver/vagrant_spec.rbfor the tart provider VM naming behaviorvendordirectory to prevent bundler dependencies from being committed to the repositoryBackground
The tart provider (https://github.com/letiemble/vagrant-tart) for Vagrant enables Test Kitchen to work with tart VMs (https://github.com/cirruslabs/tart). This PR follows the review feedback suggesting to consolidate duplicate case statements rather than having separate blocks for VM name configuration.
Testing
The changes are minimal and focused, following existing code patterns in the repository.
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.