added vagrant upload account configuration in builds.yml

[Stromweld]

Description

added vagrant upload account configuration in builds.yml and defaulting hyperv to generation 2

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)
• [ ] Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

• [x] I have read the CONTRIBUTING document.
• [x] I have run the pre-merge tests locally and they pass.
• [x] I have updated the documentation accordingly.
• [x] I have added tests to cover my changes.
• [x] All new and existing tests passed.
• [x] All commits have been signed-off for the Developer Certificate of Origin.

[hunleyd]

hey @Stromweld for those of us who use this repo to manage our own 'fleet' of Vagrant images for our company.. do you have plans to expand this PR to allow us to specify the account name and if the box should be public/private? Or is this just for bento use and we should continue to use our current upload logic?

[Stromweld]

Once this is merged in the builds.yml file you can specify the account you want vagrant to upload the boxes to. it'll default to bento but if you manage your own fork then you can change it to your account. You simply need to have logged-in to the account with the vagrant cli for the session token. Bento is simply then running vagrant cloud plublish <acct_name>/<box_name> command. You'll get the same box names and descriptions as the bento released ones though.

[Stromweld]

Currently it's publishing all boxes publicly but I can add to it the ability to define in the builds.yml file which will be public and default to private otherwise.

[sonarcloud[bot]]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication