gusztavvargadr/vagrant

Improve YAML configuration

Closed this issue · 1 comments

gusztavvargadr commented

Summary

  • Convert to plugin
    • Vagrantcomponent / Vagrantbuilder
    • Support custom ruby extensions for components
    • factory methods for parents (e.g. deployment.machine instead of VagrantMachine.configure)
    • 'defaults' to base / core
  • Allow use together with standard Vagrant configs
  • Review Vagrant options from new version
    • Vagrant version to conf
    • Make options future proof (use hash insteaf of named keys)
    • Magic constants (defaults and else)
    • Symbolize keys
    • Named params instead of options on classes
    • Blocks to change configuration (similar to core vagrant)
  • Move synced folders into providers / provisioners
    • Use named hash keys instead of folder names
    • Review domain name issues with Linux / Windows
  • Review issues with Powershell on Windows
  • Review WinSSH options
  • Environment variables to options (VAGRANT_VAR)
  • Environment name load from folder (check with kitchen)
    • review machine and deployment names
    • options for vm name
  • Get deployment directory from Vagrant
  • Check for directory absolute paths
  • Hyper-V
    • Dynamic memory
  • Machine profiles
    • Size for local and cloud
    • OS for local and cloud
  • Add support for triggers
  • SMB
    • smb host ip
    • smb user with domain
    • synced folders external share
  • Naming for run provisioner
gusztavvargadr commented

Closed as obsolete.