Merge pull request #25657 from pdecat/typo_hierarchical
Typo: heirarchical => hierarchical
This commit is contained in:
commit
f2d213c461
|
@ -25,7 +25,7 @@ import (
|
|||
//
|
||||
// The provider-related functions live primarily in meta_providers.go, and
|
||||
// lean on some different underlying mechanisms in order to support automatic
|
||||
// installation and a heirarchical addressing namespace, neither of which
|
||||
// installation and a hierarchical addressing namespace, neither of which
|
||||
// are supported for other plugin types.
|
||||
|
||||
// store the user-supplied path for plugin discovery
|
||||
|
|
|
@ -461,7 +461,7 @@ func (addr *ResourceAddress) Contains(other *ResourceAddress) bool {
|
|||
// equality. Instead, it tests that the _specified_ parts of each
|
||||
// address match, treating any unspecified parts as wildcards.
|
||||
//
|
||||
// See also Contains, which takes a more heirarchical approach to comparing
|
||||
// See also Contains, which takes a more hierarchical approach to comparing
|
||||
// addresses.
|
||||
func (addr *ResourceAddress) Equals(raw interface{}) bool {
|
||||
other, ok := raw.(*ResourceAddress)
|
||||
|
|
|
@ -219,7 +219,7 @@ elements in the input variables.
|
|||
|
||||
* [`contains`](./contains.html) tests whether a given list or set contains
|
||||
a given element value.
|
||||
* [`flatten`](./flatten.html) is useful for flattening heirarchical data
|
||||
* [`flatten`](./flatten.html) is useful for flattening hierarchical data
|
||||
into a single list, for situations where the relationships between two
|
||||
object types are defined explicitly.
|
||||
* [`setintersection`](./setintersection.html) computes the _intersection_ of
|
||||
|
|
|
@ -32,7 +32,7 @@ resource "aws_subnet" "example" {
|
|||
}
|
||||
```
|
||||
|
||||
When we introduce `module` blocks, our configuration becomes heirarchical
|
||||
When we introduce `module` blocks, our configuration becomes hierarchical
|
||||
rather than flat: each module contains its own set of resources, and possibly
|
||||
its own child modules, which can potentially create a deep, complex tree of
|
||||
resource configurations.
|
||||
|
|
Loading…
Reference in New Issue