Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

provider/aws: data sources for AWS network planning #6819

Merged
merged 7 commits into from
Oct 13, 2016
Merged

provider/aws: data sources for AWS network planning #6819

merged 7 commits into from
Oct 13, 2016

Commits on Sep 24, 2016

  1. core: don't force data resource id diff to be empty 

    In an attempt to always show "id" as computed we were producing a
synthetic diff for it, but this causes problems when the id attribute for
a particular data source is actually settable in configuration, since it
masks the setting from the config and forces it to always be empty.

Instead, we'll set it conditionally so that a value provided in the config
can shine through when available.
    @apparentlymart
    apparentlymart committed Sep 24, 2016
    Configuration menu
    Copy the full SHA
    ab29eca View commit details
    Browse the repository at this point in the history

  2. provider/aws: utilities for building EC2 filter sets 

    These functions can be used within various EC2 data sources to support
querying by filter. The following cases are supported:

- Filtering by exact equality with single attribute values
- Filtering by EC2 tag key/value pairs
- Explicitly specifying raw EC2 filters in config

This should cover most of the filter use-cases for Terraform data
sources that are built on EC2's 'Describe...' family of functions.
    @apparentlymart
    apparentlymart committed Sep 24, 2016
    Configuration menu
    Copy the full SHA
    de51398 View commit details
    Browse the repository at this point in the history

  3. provider/aws: aws_subnet data source

    @apparentlymart
    apparentlymart committed Sep 24, 2016
    Configuration menu
    Copy the full SHA
    82f958c View commit details
    Browse the repository at this point in the history

  4. provider/aws: aws_vpc data source

    @apparentlymart
    apparentlymart committed Sep 24, 2016
    Configuration menu
    Copy the full SHA
    aa0b601 View commit details
    Browse the repository at this point in the history

  5. provider/aws: availability zone data source 

    This adds a singular data source in addition to the existing plural one.
This allows retrieving data about a specific AZ.

As a helper for writing reusable modules, the AZ letter (without its
usual region name prefix) is exposed so that it can be used in
region-agnostic mappings where a different value is used per AZ, such as
for subnet numbering schemes.
    @apparentlymart
    apparentlymart committed Sep 24, 2016
    Configuration menu
    Copy the full SHA
    fca9216 View commit details
    Browse the repository at this point in the history

  6. provider/aws: aws_region data source 

    The primary purpose of this data source is to ask the question "what is
my current region?", but it can also be used to retrieve the endpoint
hostname for a particular (possibly non-current) region, should that be
useful for some esoteric case.
    @apparentlymart
    apparentlymart committed Sep 24, 2016
    Configuration menu
    Copy the full SHA
    94c45c6 View commit details
    Browse the repository at this point in the history

  7. examples: creating VPCs and subnets across two regions 

    This example demonstrates both creating a network architecture *and* the
use of data resources to minimize the number of variables needed for a
child module by discovering additional data automatically.
    @apparentlymart
    apparentlymart committed Sep 24, 2016
    Configuration menu
    Copy the full SHA
    0e3256b View commit details
    Browse the repository at this point in the history