From 8f59f89a2efc467617e043c35bcee7698909a182 Mon Sep 17 00:00:00 2001 From: Seth Vargo Date: Tue, 4 Nov 2014 10:44:44 -0500 Subject: [PATCH] Explain that older Vagrant plugin licenses may not work with new VMware This is the result of an unhappy customer who raised a very valid point. If you are not on the Vagrant mailing list, you would be unaware that upgrading VMware would cause your plugin to stop functioning. While this does not solve the problem of dispersing that information, it helps clarify that plugin version support is for the latest version of the Vagrant plugin and does not extend to previous ones. --- website/www/source/vmware/index.html.erb | 3 +++ 1 file changed, 3 insertions(+) diff --git a/website/www/source/vmware/index.html.erb b/website/www/source/vmware/index.html.erb index fa5ed565d..9d1b8b8fb 100644 --- a/website/www/source/vmware/index.html.erb +++ b/website/www/source/vmware/index.html.erb @@ -176,6 +176,9 @@ page_title: "VMware Vagrant Environments" The provider license does not include a license to the VMware software, which must be purchased separately. If you're buying over 100 licenses, contact sales@hashicorp.com for volume pricing. +
+ Previous plugin versions may not support the latest VMware products. Please visit the license upgrade center to check if your license requires an upgrade before you upgrade your VMware products. +
For reseller information, click here.