-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
added vagrant upload account configuration in builds.yml #1522
Conversation
…ng hyperv to generation 2 Signed-off-by: Corey Hemminger <[email protected]>
Signed-off-by: Corey Hemminger <[email protected]>
Signed-off-by: Corey Hemminger <[email protected]>
Signed-off-by: Corey Hemminger <[email protected]>
Signed-off-by: Corey Hemminger <[email protected]>
Signed-off-by: Corey Hemminger <[email protected]>
Signed-off-by: Corey Hemminger <[email protected]>
Signed-off-by: Corey Hemminger <[email protected]>
Signed-off-by: Corey Hemminger <[email protected]>
Signed-off-by: Corey Hemminger <[email protected]>
Signed-off-by: Corey Hemminger <[email protected]>
Signed-off-by: Corey Hemminger <[email protected]>
…es flags, fixed upload description for libvirt to add qemu hv and version, removed debian 10, updated ubuntu 20.04 boot_command, changed workflows to be based on cpu architecture Signed-off-by: Corey Hemminger <[email protected]>
Signed-off-by: Corey Hemminger <[email protected]>
Signed-off-by: Corey Hemminger <[email protected]>
Signed-off-by: Corey Hemminger <[email protected]>
Signed-off-by: Corey Hemminger <[email protected]>
Signed-off-by: Corey Hemminger <[email protected]>
Signed-off-by: Corey Hemminger <[email protected]>
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? |
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 |
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. |
Signed-off-by: Corey Hemminger <[email protected]>
Signed-off-by: Corey Hemminger <[email protected]>
Signed-off-by: Corey Hemminger <[email protected]>
Signed-off-by: Corey Hemminger <[email protected]>
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
* 'main' of github.com:chef/bento: added vagrant upload account configuration in builds.yml (chef#1522)
Description
added vagrant upload account configuration in builds.yml and defaulting hyperv to generation 2
Types of changes
Checklist: