Bump github.com/hashicorp/hcl/v2 from 2.6.0 to 2.9.1

[dependabot]

Bumps github.com/hashicorp/hcl/v2 from 2.6.0 to 2.9.1.

Release notes

Sourced from github.com/hashicorp/hcl/v2's releases.

v2.9.1

Bugs Fixed

• hclsyntax: Fix panic for marked index value. (#451)

v2.8.2

Bugs Fixed

• hclsyntax: Fix panic for marked collection splat. (#436)
• hclsyntax: Fix panic for marked template loops. (#437)
• hclsyntax: Fix for expression marked conditional.(#438)
• hclsyntax: Mark objects with keys that are sensitive. (#440)

v2.8.1

Bugs Fixed

• hclsyntax: Fix panic when expanding marked function arguments. (#429)
• hclsyntax: Error when attempting to use a marked value as an object key. (#434)
• hclsyntax: Error when attempting to use a marked value as an object key in expressions. (#433)

v2.8.0

Enhancements

• hclsyntax: Expression grouping parentheses will now be reflected by an explicit node in the AST, whereas before they were only considered during parsing. (#426)

Bugs Fixed

• hclwrite: The parser will now correctly include the ( and ) tokens when an expression is surrounded by parentheses. Previously it would incorrectly recognize those tokens as being extraneous tokens outside of the expression. (#426)
• hclwrite: The formatter will now remove (rather than insert) spaces between the ! (unary boolean "not") operator and its subsequent operand. (#403)
• hclsyntax: Unmark conditional values in expressions before checking their truthfulness (#427)

v2.7.2

Bugs Fixed

• gohcl: Fix panic when decoding into type containing value slices. (#335)
• hclsyntax: The unusual expression null[*] was previously always returning an unknown value, even though the rules for [*] normally call for it to return an empty tuple when applied to a null. As well as being a surprising result, it was particularly problematic because it violated the rule that a calling application may assume that an expression result will always be known unless the application itself introduces unknown values via the evaluation context. null[*] will now produce an empty tuple. (#416)
• hclsyntax: Fix panic when traversing a list, tuple, or map with cty "marks" (#424)

v2.7.1

Bugs Fixed

• hclwrite: Correctly handle blank quoted string block labels, instead of dropping them (#422)

v2.7.0

Enhancements

• json: There is a new function ParseWithStartPos, which allows overriding the starting position for parsing in case the given JSON bytes are a fragment of a larger document, such as might happen when decoding with encoding/json into a json.RawMessage. (#389)
• json: There is a new function ParseExpression, which allows parsing a JSON string directly in expression mode, whereas previously it was only possible to parse a JSON string in body mode. (#381)
• hclwrite: Block type now supports SetType and SetLabels, allowing surgical changes to the type and labels of an existing block without having to reconstruct the entire block. (#340)

Bugs Fixed

... (truncated)

Changelog

Sourced from github.com/hashicorp/hcl/v2's changelog.

v2.9.1 (March 10, 2021)

Bugs Fixed

• hclsyntax: Fix panic for marked index value. (#451)

v2.9.0 (February 23, 2021)

Enhancements

• HCL's native syntax and JSON scanners -- and thus all of the other parsing components that build on top of them -- are now using Unicode 13 rules for text segmentation when counting text characters for the purpose of reporting source location columns. Previously HCL was using Unicode 12. Unicode 13 still uses the same algorithm but includes some additions to the character tables the algorithm is defined in terms of, to properly categorize new characters defined in Unicode 13.

v2.8.2 (January 6, 2021)

Bugs Fixed

• hclsyntax: Fix panic for marked collection splat. (#436)
• hclsyntax: Fix panic for marked template loops. (#437)
• hclsyntax: Fix for expression marked conditional. (#438)
• hclsyntax: Mark objects with keys that are sensitive. (#440)

v2.8.1 (December 17, 2020)

Bugs Fixed

• hclsyntax: Fix panic when expanding marked function arguments. (#429)
• hclsyntax: Error when attempting to use a marked value as an object key. (#434)
• hclsyntax: Error when attempting to use a marked value as an object key in expressions. (#433)

v2.8.0 (December 7, 2020)

Enhancements

• hclsyntax: Expression grouping parentheses will now be reflected by an explicit node in the AST, whereas before they were only considered during parsing. (#426)

Bugs Fixed

• hclwrite: The parser will now correctly include the ( and ) tokens when an expression is surrounded by parentheses. Previously it would incorrectly recognize those tokens as being extraneous tokens outside of the expression. (#426)
• hclwrite: The formatter will now remove (rather than insert) spaces between the ! (unary boolean "not") operator and its subsequent operand. (#403)
• hclsyntax: Unmark conditional values in expressions before checking their truthfulness (#427)

v2.7.2 (November 30, 2020)

Bugs Fixed

• gohcl: Fix panic when decoding into type containing value slices. (#335)
• hclsyntax: The unusual expression null[*] was previously always returning an unknown value, even though the rules for [*] normally call for it to return an empty tuple when applied to a null. As well as being a surprising result, it was particularly problematic because it violated the rule that a calling application may assume that an expression result will always be known unless the application itself introduces unknown values via the evaluation context. null[*] will now produce an empty tuple. (#416)
• hclsyntax: Fix panic when traversing a list, tuple, or map with cty "marks" (#424)

v2.7.1 (November 18, 2020)

... (truncated)

Commits

• 805c25b update CHANGELOG.md
• d7e7bca Merge pull request #451 from hashicorp/jbardin/marked-index
• ab5bd03 avoid panics with marked index values
• 2cbe9e4 v2.9.0 release
• 1540ea0 Update CHANGELOG.md
• 7887810 specsuite: Fix some regressions
• 2eaeb36 Use Unicode 13 text segmentation rules
• 2520246 Merge pull request #444 from hashicorp/jbardin/hcltest-expr-map
• 94baef9 add an ExprMap method to the mock expression
• 41e4082 Update CHANGELOG.md
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #37.