Skip to content
This repository has been archived by the owner on Sep 30, 2020. It is now read-only.

Use existing subnets when creating/updating cluster #227

Merged
merged 6 commits into from
Jan 24, 2017

Commits on Jan 19, 2017

  1. Launch in existing subnets

    Saso Matejina committed Jan 19, 2017
    Configuration menu
    Copy the full SHA
    8820e8e View commit details
    Browse the repository at this point in the history
  2. Validate update and export

    Saso Matejina committed Jan 19, 2017
    Configuration menu
    Copy the full SHA
    dc4cdc2 View commit details
    Browse the repository at this point in the history
  3. Fix test data

    Saso Matejina committed Jan 19, 2017
    Configuration menu
    Copy the full SHA
    f034cbb View commit details
    Browse the repository at this point in the history
  4. Move r53 schecks to create, update nodepool stack template

    Saso Matejina committed Jan 19, 2017
    Configuration menu
    Copy the full SHA
    2c9e398 View commit details
    Browse the repository at this point in the history
  5. fixing subnet refs

    jeremyd authored and Saso Matejina committed Jan 19, 2017
    Configuration menu
    Copy the full SHA
    c7ee3a1 View commit details
    Browse the repository at this point in the history
  6. Don't try to validate config during update

    redbaron authored and Saso Matejina committed Jan 19, 2017
    Configuration menu
    Copy the full SHA
    bc7c8a1 View commit details
    Browse the repository at this point in the history