-
Notifications
You must be signed in to change notification settings - Fork 49
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
New virtualization tool set (and new aet-cookbook version) #301
Conversation
# Conflicts: # CHANGELOG.md
# Conflicts (resolved): # CHANGELOG.md # documentation/src/main/wiki/AETIn10Minutes.md # documentation/src/main/wiki/BasicSetup.md # vagrant/README.md
…le plugin from Maven
vagrant/Vagrantfile
Outdated
@@ -96,7 +96,7 @@ Vagrant.configure(VAGRANTFILE_API_VERSION) do |config| | |||
} | |||
} | |||
chef.run_list = [ | |||
"recipe[aet::_develop]", | |||
# "recipe[aet::_develop]", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for this PR @wiiitek :)
I think we should use aet::_develop
by default on Vagrant - it creates developer
user which allows us to easily upload AET to Vagrant with maven using developer/developer
credentials, as instructed in AET in 10 minutes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're right! This change was to test the use case described in wttech/aet-cookbook#30 (comment). I will revert this change. We should probably do a release for the aet-cookbook (version 5.0.0). What do you think?
Upgrade for our virtualization tools to:
Description
Updates made fr cookbook are on separate branch. This branch is specified in
Berksfile
.When we are ready to merge (tests on different environments for new AET 10 minut setup) we would need to release new aet-cookbook version.
Motivation and Context
New Virtualbox and Chef will allow us to make progress into Windows environments more easily.
And we also don't want to use some old, non-supported versions (VirtualBox 5.1.x is no longer supported!).
Types of changes
Checklist:
I hereby agree to the terms of the AET Contributor License Agreement.