Browse Source
ewencp This small change allows users to use Vagrantfile.local to specify a custom prefix for names of ec2 instances brought up with vagrant. This makes management of multiple aws test clusters a little easier since individual clusters can be assigned different name prefixes. if `ec2_instance_name_prefix` is not specified in `Vagrantfile.local`, behavior will be exactly the same as before this change. Testing: - aws: I verified worker nodes, broker nodes, zk nodes with and without the prefix override. Behavior is as expected - locally: I verified that bringing up worker nodes, broker nodes, zk nodes on a local machine is not impacted by this change. Author: Geoff Anderson <geoff@confluent.io> Reviewers: Ewen Cheslack-Postava <ewen@confluent.io> Closes #801 from granders/minor-vagrant-aws-overrideable-prefixpull/799/merge
Geoff Anderson
9 years ago
committed by
Ewen Cheslack-Postava
1 changed files with 6 additions and 5 deletions
Loading…
Reference in new issue