This project is mirrored from https://:*****@github.com/hashicorp/terraform.git. Pull mirroring failed .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
  1. 01 Apr, 2019 2 commits
  2. 29 Mar, 2019 11 commits
  3. 28 Mar, 2019 12 commits
    • Kristin Laemmert's avatar
      configupgrade: fix test (#20863) · da521707
      Kristin Laemmert authored
      da521707
    • Pam Selle's avatar
      Update CHANGELOG.md · 4c1bb8ab
      Pam Selle authored
      4c1bb8ab
    • Kristin Laemmert's avatar
      configs/configupgrade: detect invalid resource names and print a TODO (#20856) · 1baa1b90
      Kristin Laemmert authored
      
      * configs/configupgrade: detect invalid resource names and print a TODO
      message
      
      In terraform 0.11 and prior it was possible to start a resource name
      with a number. This is no longer valid, as the resource name would would
      be ambiguous with number values in HCL expressions.
      
      Fixes #19919
      
      * Update configs/configupgrade/test-fixtures/valid/invalid-resource-name/want/resource.tf
      Co-Authored-By: default avatarmildwonkey <mildwonkey@users.noreply.github.com>
      1baa1b90
    • Martin Atkins's avatar
      lang: Detect references when a list/set attr is defined using blocks · 003317d7
      Martin Atkins authored
      For compatibility with documented patterns from existing providers we are
      now allowing (via a pre-processing step) any attribute whose type is a
      list-of-object or set-of-object type to optionally be assigned using one
      or more blocks whose type is the attribute name.
      
      The pre-processing functionality was implemented in previous commits but
      we were not correctly detecting references within these blocks that are,
      from the perspective of the primary schema, invalid. Now we'll use an
      alternative implementation of variable detection that is able to apply the
      same schema rewriting technique we used to implement the transform and
      thus can find all of the references as if they were already in their
      final locations.
      003317d7
    • Martin Atkins's avatar
      lang/blocktoattr: ExpandedVariables function · 8746e9e8
      Martin Atkins authored
      Because we handle FixUpBlockAttrs after dynamic block expansion, when
      resolving variables we unfortunately need to consider the possibility of
      both dynamic block expansion _and_ the block attrs fixup.
      
      To accommodate this we have a variant of dynblock.VariablesHCLDec that
      instead walks using the configschema.Block representation of the schema
      and applies the same opportunistic schema rewrite used by FixUpBlockAttrs
      at each body encountered during the walk.
      8746e9e8
    • Martin Atkins's avatar
      vendor: go get github.com/hashicorp/hcl2@master · b35bc255
      Martin Atkins authored
      This gives us an extra hook in the dynblock variables analysis that should
      allow us to also make it subject also to the lang/blocktoattr fixup, to
      ensure we'll find all the references in spite of these various
      pre-processing wrappers.
      b35bc255
    • Martin Atkins's avatar
      lang/eval: Apply attr-as-nested-block fixup in EvalBlock · 87786484
      Martin Atkins authored
      For any block content we evaluate dynamically via this API, we'll make a
      special allowance for users to optionally write members of a list
      attribute instead as a sequence of nested blocks, thus allowing some
      existing provider features that were assuming this capability to continue
      to support it after v0.12.
      
      This should not be used for any new provider features, and should ideally
      be eventually phased out so that there aren't two
      similar-but-slightly-different syntaxes for saying the same thing.
      87786484
    • Martin Atkins's avatar
      lang/blocktoattr: Selectively allow block syntax to be used for attributes · 6dcf8195
      Martin Atkins authored
      This preprocessing step allows users to use nested block syntax to specify
      elements of an attribute that is defined as being a list or set of an
      object type.
      
      This restores part of the unintended flexibility permitted in Terraform
      v0.11 so that we can work around a few tricky edges where provider
      implementations were relying on Terraform's failure to validate this in
      earlier versions.
      
      For any body that is pre-processed using this new helper, we will
      recognize when a configuration author uses nested block syntax with a
      name that is specified in the schema as an attribute of a suitable type
      and tweak the schema just in time before decoding to expect that usage
      and then fix up the result on the way out to conform to the original
      schema.
      
      Achieving this requires an abstraction inversion because only Terraform's
      high-level schema has enough information to decide how to rewrite the
      incoming low-level schema. We must therefore here implement HCL's
      lowest-level API interface in terms of the higher-level abstractions of
      hcldec and Terraform's configschema.
      
      Because of the abstraction inversion this fixup mechanism cannot be used
      generally for arbitrary HCL bodies but we can use it carefully inside the
      lang package where its own API can guarantee the necessary invariants for
      this to work.
      6dcf8195
    • Pam Selle's avatar
      Merge pull request #20853 from pselle/err-handling-registry-unresponsive · d1c1bc6c
      Pam Selle authored
      Add friendly error for when registry unresponsive
      d1c1bc6c
    • Sander van Harmelen's avatar
      backend/remote: correctly load remote variables · 39a95e42
      Sander van Harmelen authored
      When using `terraform console` in combination with the remote backend, variables defined in Terraform Enterprise were load loaded correctly.
      39a95e42
    • Kristin Laemmert's avatar
      931851ca
    • Sander van Harmelen's avatar
      Merge pull request #20843 from hashicorp/svh/f-force-push · 86164c0b
      Sander van Harmelen authored
      backend/local: preserve serial and lineage on failure
      86164c0b
  4. 27 Mar, 2019 6 commits
  5. 26 Mar, 2019 3 commits
  6. 25 Mar, 2019 6 commits