kafka-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From gwens...@apache.org
Subject [kafka] branch trunk updated: MINOR: Add missing option for running vagrant-up.sh with AWS to vagrant/README.md
Date Fri, 10 May 2019 05:51:30 GMT
This is an automated email from the ASF dual-hosted git repository.

gwenshap pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/kafka.git


The following commit(s) were added to refs/heads/trunk by this push:
     new 31859a4  MINOR: Add missing option for running vagrant-up.sh with AWS to vagrant/README.md
31859a4 is described below

commit 31859a452b68ddd98281ff341a6b75c579f3c050
Author: Kengo Seki <sekikn@apache.org>
AuthorDate: Thu May 9 22:51:10 2019 -0700

    MINOR: Add missing option for running vagrant-up.sh with AWS to vagrant/README.md
    
    Contrary to the previous explanation, a command example in
    vagrant/README.md lacks the option to specify the aws provider.
    
    Author: Kengo Seki <sekikn@apache.org>
    
    Reviewers: Gwen Shapira
    
    Closes #6702 from sekikn/add-missing-option
---
 vagrant/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/vagrant/README.md b/vagrant/README.md
index f5171c2..f482f04 100644
--- a/vagrant/README.md
+++ b/vagrant/README.md
@@ -127,7 +127,7 @@ Next, configure parameters in `Vagrantfile.local`. A few are *required*:
 
 Now start things up, but specify the aws provider:
 
-    $ vagrant/vagrant-up.sh
+    $ vagrant/vagrant-up.sh --aws
 
 Your instances should get tagged with a name including your hostname to make
 them identifiable and make it easier to track instances in the AWS management


Mime
View raw message