ResiLien
/
terraform
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
terraform/website/layouts/functions.erb

458 lines
19 KiB
Plaintext
Raw Normal View History

website: Beginnings of "Functions" configuration section Previously we just listed out all of the functions in alphabetical order inside the "Interpolation Syntax" page, but that format doesn't leave much room for details and usage examples. Now we give each function its own page, and categorize them for easier navigation. While many functions are very simple and don't really warrant a full page, certain functions do have additional details that are worth mentioning and this structure scales better for those more complicated functions. So far this includes only the numeric and string functions. Other categories will follow in subsequent commits.
2018-05-07 03:32:16 +02:00
<% wrap_layout :inner do %>
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<% content_for :sidebar do %>
<h4><a href="/docs/index.html">Terraform CLI</a></h4>
website: Structural edit of configuration language docs This commit is a wide-ranging set of edits to the pages under /docs/configuration. Among other things, it - Separates style conventions out into their own page. - Separates type constraints and conversion info into their own page. - Conflates similar complex types a little more freely, since the distinction is only relevant when restricting inputs for a reusable module or resource. - Clarifies several concepts that confused me during edits.
2018-12-11 01:14:33 +01:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<ul class="nav docs-sidenav">
<li<%= sidebar_current("docs-config-index") %>>
<a class="back" href="/docs/configuration/index.html">Configuration Language</a>
<ul class="nav nav-visible">
website: Beginnings of "Functions" configuration section Previously we just listed out all of the functions in alphabetical order inside the "Interpolation Syntax" page, but that format doesn't leave much room for details and usage examples. Now we give each function its own page, and categorize them for easier navigation. While many functions are very simple and don't really warrant a full page, certain functions do have additional details that are worth mentioning and this structure scales better for those more complicated functions. So far this includes only the numeric and string functions. Other categories will follow in subsequent commits.
2018-05-07 03:32:16 +02:00
<li<%= sidebar_current("docs-config-functions") %>>
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<a href="/docs/configuration/functions.html">Functions</a>
<ul class="nav nav-visible">
<li id="docs-funcs-numeric"<%= sidebar_current("docs-funcs-numeric") %>>
<a href="#docs-funcs-numeric">Numeric Functions</a>
<ul class="nav nav-visible">
website: Structural edit of configuration language docs This commit is a wide-ranging set of edits to the pages under /docs/configuration. Among other things, it - Separates style conventions out into their own page. - Separates type constraints and conversion info into their own page. - Conflates similar complex types a little more freely, since the distinction is only relevant when restricting inputs for a reusable module or resource. - Clarifies several concepts that confused me during edits.
2018-12-11 01:14:33 +01:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-numeric-abs") %>>
<a href="/docs/configuration/functions/abs.html">abs</a>
</li>
website: Beginnings of "Functions" configuration section Previously we just listed out all of the functions in alphabetical order inside the "Interpolation Syntax" page, but that format doesn't leave much room for details and usage examples. Now we give each function its own page, and categorize them for easier navigation. While many functions are very simple and don't really warrant a full page, certain functions do have additional details that are worth mentioning and this structure scales better for those more complicated functions. So far this includes only the numeric and string functions. Other categories will follow in subsequent commits.
2018-05-07 03:32:16 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-numeric-ceil") %>>
<a href="/docs/configuration/functions/ceil.html">ceil</a>
</li>
website: Beginnings of "Functions" configuration section Previously we just listed out all of the functions in alphabetical order inside the "Interpolation Syntax" page, but that format doesn't leave much room for details and usage examples. Now we give each function its own page, and categorize them for easier navigation. While many functions are very simple and don't really warrant a full page, certain functions do have additional details that are worth mentioning and this structure scales better for those more complicated functions. So far this includes only the numeric and string functions. Other categories will follow in subsequent commits.
2018-05-07 03:32:16 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-numeric-floor") %>>
<a href="/docs/configuration/functions/floor.html">floor</a>
</li>
website: Beginnings of "Functions" configuration section Previously we just listed out all of the functions in alphabetical order inside the "Interpolation Syntax" page, but that format doesn't leave much room for details and usage examples. Now we give each function its own page, and categorize them for easier navigation. While many functions are very simple and don't really warrant a full page, certain functions do have additional details that are worth mentioning and this structure scales better for those more complicated functions. So far this includes only the numeric and string functions. Other categories will follow in subsequent commits.
2018-05-07 03:32:16 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-numeric-log") %>>
<a href="/docs/configuration/functions/log.html">log</a>
</li>
website: Beginnings of "Functions" configuration section Previously we just listed out all of the functions in alphabetical order inside the "Interpolation Syntax" page, but that format doesn't leave much room for details and usage examples. Now we give each function its own page, and categorize them for easier navigation. While many functions are very simple and don't really warrant a full page, certain functions do have additional details that are worth mentioning and this structure scales better for those more complicated functions. So far this includes only the numeric and string functions. Other categories will follow in subsequent commits.
2018-05-07 03:32:16 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-numeric-max") %>>
<a href="/docs/configuration/functions/max.html">max</a>
</li>
website: Beginnings of "Functions" configuration section Previously we just listed out all of the functions in alphabetical order inside the "Interpolation Syntax" page, but that format doesn't leave much room for details and usage examples. Now we give each function its own page, and categorize them for easier navigation. While many functions are very simple and don't really warrant a full page, certain functions do have additional details that are worth mentioning and this structure scales better for those more complicated functions. So far this includes only the numeric and string functions. Other categories will follow in subsequent commits.
2018-05-07 03:32:16 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-numeric-min") %>>
<a href="/docs/configuration/functions/min.html">min</a>
</li>
website: Beginnings of "Functions" configuration section Previously we just listed out all of the functions in alphabetical order inside the "Interpolation Syntax" page, but that format doesn't leave much room for details and usage examples. Now we give each function its own page, and categorize them for easier navigation. While many functions are very simple and don't really warrant a full page, certain functions do have additional details that are worth mentioning and this structure scales better for those more complicated functions. So far this includes only the numeric and string functions. Other categories will follow in subsequent commits.
2018-05-07 03:32:16 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-numeric-pow") %>>
<a href="/docs/configuration/functions/pow.html">pow</a>
</li>
website: Beginnings of "Functions" configuration section Previously we just listed out all of the functions in alphabetical order inside the "Interpolation Syntax" page, but that format doesn't leave much room for details and usage examples. Now we give each function its own page, and categorize them for easier navigation. While many functions are very simple and don't really warrant a full page, certain functions do have additional details that are worth mentioning and this structure scales better for those more complicated functions. So far this includes only the numeric and string functions. Other categories will follow in subsequent commits.
2018-05-07 03:32:16 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-numeric-signum") %>>
<a href="/docs/configuration/functions/signum.html">signum</a>
</li>
website: Beginnings of "Functions" configuration section Previously we just listed out all of the functions in alphabetical order inside the "Interpolation Syntax" page, but that format doesn't leave much room for details and usage examples. Now we give each function its own page, and categorize them for easier navigation. While many functions are very simple and don't really warrant a full page, certain functions do have additional details that are worth mentioning and this structure scales better for those more complicated functions. So far this includes only the numeric and string functions. Other categories will follow in subsequent commits.
2018-05-07 03:32:16 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
</ul>
website: Beginnings of "Functions" configuration section Previously we just listed out all of the functions in alphabetical order inside the "Interpolation Syntax" page, but that format doesn't leave much room for details and usage examples. Now we give each function its own page, and categorize them for easier navigation. While many functions are very simple and don't really warrant a full page, certain functions do have additional details that are worth mentioning and this structure scales better for those more complicated functions. So far this includes only the numeric and string functions. Other categories will follow in subsequent commits.
2018-05-07 03:32:16 +02:00
</li>
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li id="docs-funcs-string"<%= sidebar_current("docs-funcs-string") %>>
<a href="#docs-funcs-string">String Functions</a>
<ul class="nav nav-visible">
website: Beginnings of "Functions" configuration section Previously we just listed out all of the functions in alphabetical order inside the "Interpolation Syntax" page, but that format doesn't leave much room for details and usage examples. Now we give each function its own page, and categorize them for easier navigation. While many functions are very simple and don't really warrant a full page, certain functions do have additional details that are worth mentioning and this structure scales better for those more complicated functions. So far this includes only the numeric and string functions. Other categories will follow in subsequent commits.
2018-05-07 03:32:16 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-string-chomp") %>>
<a href="/docs/configuration/functions/chomp.html">chomp</a>
</li>
website: Beginnings of "Functions" configuration section Previously we just listed out all of the functions in alphabetical order inside the "Interpolation Syntax" page, but that format doesn't leave much room for details and usage examples. Now we give each function its own page, and categorize them for easier navigation. While many functions are very simple and don't really warrant a full page, certain functions do have additional details that are worth mentioning and this structure scales better for those more complicated functions. So far this includes only the numeric and string functions. Other categories will follow in subsequent commits.
2018-05-07 03:32:16 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-string-format-x") %>>
<a href="/docs/configuration/functions/format.html">format</a>
</li>
website: Beginnings of "Functions" configuration section Previously we just listed out all of the functions in alphabetical order inside the "Interpolation Syntax" page, but that format doesn't leave much room for details and usage examples. Now we give each function its own page, and categorize them for easier navigation. While many functions are very simple and don't really warrant a full page, certain functions do have additional details that are worth mentioning and this structure scales better for those more complicated functions. So far this includes only the numeric and string functions. Other categories will follow in subsequent commits.
2018-05-07 03:32:16 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-string-formatlist") %>>
<a href="/docs/configuration/functions/formatlist.html">formatlist</a>
</li>
website: Beginnings of "Functions" configuration section Previously we just listed out all of the functions in alphabetical order inside the "Interpolation Syntax" page, but that format doesn't leave much room for details and usage examples. Now we give each function its own page, and categorize them for easier navigation. While many functions are very simple and don't really warrant a full page, certain functions do have additional details that are worth mentioning and this structure scales better for those more complicated functions. So far this includes only the numeric and string functions. Other categories will follow in subsequent commits.
2018-05-07 03:32:16 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-string-indent") %>>
<a href="/docs/configuration/functions/indent.html">indent</a>
</li>
website: Beginnings of "Functions" configuration section Previously we just listed out all of the functions in alphabetical order inside the "Interpolation Syntax" page, but that format doesn't leave much room for details and usage examples. Now we give each function its own page, and categorize them for easier navigation. While many functions are very simple and don't really warrant a full page, certain functions do have additional details that are worth mentioning and this structure scales better for those more complicated functions. So far this includes only the numeric and string functions. Other categories will follow in subsequent commits.
2018-05-07 03:32:16 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-string-join") %>>
<a href="/docs/configuration/functions/join.html">join</a>
</li>
website: Beginnings of "Functions" configuration section Previously we just listed out all of the functions in alphabetical order inside the "Interpolation Syntax" page, but that format doesn't leave much room for details and usage examples. Now we give each function its own page, and categorize them for easier navigation. While many functions are very simple and don't really warrant a full page, certain functions do have additional details that are worth mentioning and this structure scales better for those more complicated functions. So far this includes only the numeric and string functions. Other categories will follow in subsequent commits.
2018-05-07 03:32:16 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-string-lower") %>>
<a href="/docs/configuration/functions/lower.html">lower</a>
</li>
website: Beginnings of "Functions" configuration section Previously we just listed out all of the functions in alphabetical order inside the "Interpolation Syntax" page, but that format doesn't leave much room for details and usage examples. Now we give each function its own page, and categorize them for easier navigation. While many functions are very simple and don't really warrant a full page, certain functions do have additional details that are worth mentioning and this structure scales better for those more complicated functions. So far this includes only the numeric and string functions. Other categories will follow in subsequent commits.
2018-05-07 03:32:16 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-string-replace") %>>
<a href="/docs/configuration/functions/replace.html">replace</a>
</li>
website: Beginnings of "Functions" configuration section Previously we just listed out all of the functions in alphabetical order inside the "Interpolation Syntax" page, but that format doesn't leave much room for details and usage examples. Now we give each function its own page, and categorize them for easier navigation. While many functions are very simple and don't really warrant a full page, certain functions do have additional details that are worth mentioning and this structure scales better for those more complicated functions. So far this includes only the numeric and string functions. Other categories will follow in subsequent commits.
2018-05-07 03:32:16 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-string-split") %>>
<a href="/docs/configuration/functions/split.html">split</a>
</li>
website: Beginnings of "Functions" configuration section Previously we just listed out all of the functions in alphabetical order inside the "Interpolation Syntax" page, but that format doesn't leave much room for details and usage examples. Now we give each function its own page, and categorize them for easier navigation. While many functions are very simple and don't really warrant a full page, certain functions do have additional details that are worth mentioning and this structure scales better for those more complicated functions. So far this includes only the numeric and string functions. Other categories will follow in subsequent commits.
2018-05-07 03:32:16 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-string-substr") %>>
<a href="/docs/configuration/functions/substr.html">substr</a>
</li>
website: Beginnings of "Functions" configuration section Previously we just listed out all of the functions in alphabetical order inside the "Interpolation Syntax" page, but that format doesn't leave much room for details and usage examples. Now we give each function its own page, and categorize them for easier navigation. While many functions are very simple and don't really warrant a full page, certain functions do have additional details that are worth mentioning and this structure scales better for those more complicated functions. So far this includes only the numeric and string functions. Other categories will follow in subsequent commits.
2018-05-07 03:32:16 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-string-title") %>>
<a href="/docs/configuration/functions/title.html">title</a>
</li>
website: Beginnings of "Functions" configuration section Previously we just listed out all of the functions in alphabetical order inside the "Interpolation Syntax" page, but that format doesn't leave much room for details and usage examples. Now we give each function its own page, and categorize them for easier navigation. While many functions are very simple and don't really warrant a full page, certain functions do have additional details that are worth mentioning and this structure scales better for those more complicated functions. So far this includes only the numeric and string functions. Other categories will follow in subsequent commits.
2018-05-07 03:32:16 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-string-trimspace") %>>
<a href="/docs/configuration/functions/trimspace.html">trimspace</a>
</li>
website: Beginnings of "Functions" configuration section Previously we just listed out all of the functions in alphabetical order inside the "Interpolation Syntax" page, but that format doesn't leave much room for details and usage examples. Now we give each function its own page, and categorize them for easier navigation. While many functions are very simple and don't really warrant a full page, certain functions do have additional details that are worth mentioning and this structure scales better for those more complicated functions. So far this includes only the numeric and string functions. Other categories will follow in subsequent commits.
2018-05-07 03:32:16 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-string-upper") %>>
<a href="/docs/configuration/functions/upper.html">upper</a>
</li>
website: Beginnings of "Functions" configuration section Previously we just listed out all of the functions in alphabetical order inside the "Interpolation Syntax" page, but that format doesn't leave much room for details and usage examples. Now we give each function its own page, and categorize them for easier navigation. While many functions are very simple and don't really warrant a full page, certain functions do have additional details that are worth mentioning and this structure scales better for those more complicated functions. So far this includes only the numeric and string functions. Other categories will follow in subsequent commits.
2018-05-07 03:32:16 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
</ul>
website: Beginnings of "Functions" configuration section Previously we just listed out all of the functions in alphabetical order inside the "Interpolation Syntax" page, but that format doesn't leave much room for details and usage examples. Now we give each function its own page, and categorize them for easier navigation. While many functions are very simple and don't really warrant a full page, certain functions do have additional details that are worth mentioning and this structure scales better for those more complicated functions. So far this includes only the numeric and string functions. Other categories will follow in subsequent commits.
2018-05-07 03:32:16 +02:00
</li>
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li id="docs-funcs-collection"<%= sidebar_current("docs-funcs-collection") %>>
<a href="#docs-funcs-collection">Collection Functions</a>
<ul class="nav nav-visible">
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-collection-chunklist") %>>
<a href="/docs/configuration/functions/chunklist.html">chunklist</a>
</li>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-collection-coalesce-x") %>>
<a href="/docs/configuration/functions/coalesce.html">coalesce</a>
</li>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-collection-coalescelist") %>>
<a href="/docs/configuration/functions/coalescelist.html">coalescelist</a>
</li>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-collection-compact") %>>
<a href="/docs/configuration/functions/compact.html">compact</a>
</li>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-collection-contains") %>>
<a href="/docs/configuration/functions/contains.html">contains</a>
</li>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-collection-distinct") %>>
<a href="/docs/configuration/functions/distinct.html">distinct</a>
</li>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-collection-element") %>>
<a href="/docs/configuration/functions/element.html">element</a>
</li>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-collection-flatten") %>>
<a href="/docs/configuration/functions/flatten.html">flatten</a>
</li>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-collection-index") %>>
<a href="/docs/configuration/functions/index.html">index</a>
</li>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-collection-keys") %>>
<a href="/docs/configuration/functions/keys.html">keys</a>
</li>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-collection-length") %>>
<a href="/docs/configuration/functions/length.html">length</a>
</li>
website: document the functions "keys", "lookup", and "values" I missed these on the first pass because in the legacy function table they are, for some reason, added in a different place than the others.
2018-06-02 03:56:34 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-collection-list") %>>
<a href="/docs/configuration/functions/list.html">list</a>
</li>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-collection-lookup") %>>
<a href="/docs/configuration/functions/lookup.html">lookup</a>
</li>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-collection-map") %>>
<a href="/docs/configuration/functions/map.html">map</a>
</li>
website: document the functions "keys", "lookup", and "values" I missed these on the first pass because in the legacy function table they are, for some reason, added in a different place than the others.
2018-06-02 03:56:34 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-collection-matchkeys") %>>
<a href="/docs/configuration/functions/matchkeys.html">matchkeys</a>
</li>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-collection-merge") %>>
<a href="/docs/configuration/functions/merge.html">merge</a>
</li>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-collection-sethaselement") %>>
<a href="/docs/configuration/functions/sethaselement.html">sethaselement</a>
</li>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-collection-setintersection") %>>
<a href="/docs/configuration/functions/setintersection.html">setintersection</a>
</li>
lang/functions: set functions from cty The sethaselement, setintersection, and setunion functions are defined in the cty stdlib. Making them available in Terraform will make it easier to work with sets, and complement the currently-Terraform-specific setproduct function. In the long run setproduct should probably move into the cty stdlib too, but since it was submitted as a Terraform function originally we'll leave it here now for simplicity's sake and reorganize later.
2019-01-15 20:51:21 +01:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-collection-setproduct") %>>
<a href="/docs/configuration/functions/setproduct.html">setproduct</a>
</li>
lang/functions: set functions from cty The sethaselement, setintersection, and setunion functions are defined in the cty stdlib. Making them available in Terraform will make it easier to work with sets, and complement the currently-Terraform-specific setproduct function. In the long run setproduct should probably move into the cty stdlib too, but since it was submitted as a Terraform function originally we'll leave it here now for simplicity's sake and reorganize later.
2019-01-15 20:51:21 +01:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-collection-setunion") %>>
<a href="/docs/configuration/functions/setunion.html">setunion</a>
</li>
lang/funcs: Convert the "setproduct" function to the new approach In our new world it produces either a set of a tuple type or a list of a tuple type, depending on the given argument types. The resulting collection's element tuple type is decided by the element types of the given collections, allowing type information to propagate even if unknown values are present.
2019-01-15 18:47:14 +01:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-collection-slice") %>>
<a href="/docs/configuration/functions/slice.html">slice</a>
</li>
lang/functions: set functions from cty The sethaselement, setintersection, and setunion functions are defined in the cty stdlib. Making them available in Terraform will make it easier to work with sets, and complement the currently-Terraform-specific setproduct function. In the long run setproduct should probably move into the cty stdlib too, but since it was submitted as a Terraform function originally we'll leave it here now for simplicity's sake and reorganize later.
2019-01-15 20:51:21 +01:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-collection-sort") %>>
<a href="/docs/configuration/functions/sort.html">sort</a>
</li>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-collection-transpose") %>>
<a href="/docs/configuration/functions/transpose.html">transpose</a>
</li>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-collection-values") %>>
<a href="/docs/configuration/functions/values.html">values</a>
</li>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-collection-zipmap") %>>
<a href="/docs/configuration/functions/zipmap.html">zipmap</a>
</li>
website: document the functions "keys", "lookup", and "values" I missed these on the first pass because in the legacy function table they are, for some reason, added in a different place than the others.
2018-06-02 03:56:34 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
</ul>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
</li>
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li id="docs-funcs-encoding"<%= sidebar_current("docs-funcs-encoding") %>>
<a href="#docs-funcs-encoding">Encoding Functions</a>
<ul class="nav nav-visible">
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-encoding-base64decode") %>>
<a href="/docs/configuration/functions/base64decode.html">base64decode</a>
</li>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-encoding-base64encode") %>>
<a href="/docs/configuration/functions/base64encode.html">base64encode</a>
</li>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-encoding-base64gzip") %>>
<a href="/docs/configuration/functions/base64gzip.html">base64gzip</a>
</li>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-encoding-csvdecode") %>>
<a href="/docs/configuration/functions/csvdecode.html">csvdecode</a>
</li>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-encoding-jsondecode") %>>
<a href="/docs/configuration/functions/jsondecode.html">jsondecode</a>
</li>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-encoding-jsonencode") %>>
<a href="/docs/configuration/functions/jsonencode.html">jsonencode</a>
</li>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-encoding-urlencode") %>>
<a href="/docs/configuration/functions/urlencode.html">urlencode</a>
</li>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
</ul>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
</li>
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li id="docs-funcs-file"<%= sidebar_current("docs-funcs-file") %>>
<a href="#docs-funcs-file">Filesystem Functions</a>
<ul class="nav nav-visible">
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-file-dirname") %>>
<a href="/docs/configuration/functions/dirname.html">dirname</a>
</li>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-file-pathexpand") %>>
<a href="/docs/configuration/functions/pathexpand.html">pathexpand</a>
</li>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-file-basename") %>>
<a href="/docs/configuration/functions/basename.html">basename</a>
</li>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-file-file-x") %>>
<a href="/docs/configuration/functions/file.html">file</a>
</li>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-file-file-exists") %>>
<a href="/docs/configuration/functions/fileexists.html">fileexists</a>
</li>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-file-filebase64") %>>
<a href="/docs/configuration/functions/filebase64.html">filebase64</a>
</li>
lang: Add fileexists function
2018-10-11 12:40:09 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-file-templatefile") %>>
<a href="/docs/configuration/functions/templatefile.html">templatefile</a>
</li>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
</ul>
lang/funcs: templatefile function This function is similar to the template_file data source offered by the template provider, but having it built in to the language makes it more convenient to use, allowing templates to be rendered from files anywhere an inline template would normally be allowed: user_data = templatefile("${path.module}/userdata.tmpl", { hostname = format("petserver%02d", count.index) }) Unlike the template_file data source, this function allows values of any type in its variables map, passing them through verbatim to the template. Its tighter integration with Terraform also allows it to return better error messages with source location information from the template itself. The template_file data source was originally created to work around the fact that HIL didn't have any support for map values at the time, and even once map support was added it wasn't very usable. With HCL2 expressions, there's little reason left to use a data source to render a template; the only remaining reason left to use template_file is to render a template that is constructed dynamically during the Terraform run, which is a very rare need.
2018-12-21 02:42:42 +01:00
</li>
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li id="docs-funcs-datetime"<%= sidebar_current("docs-funcs-datetime") %>>
<a href="#docs-funcs-datetime">Date and Time Functions</a>
<ul class="nav nav-visible">
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-datetime-timeadd") %>>
<a href="/docs/configuration/functions/timeadd.html">timeadd</a>
</li>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-datetime-timestamp") %>>
<a href="/docs/configuration/functions/timestamp.html">timestamp</a>
</li>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
</ul>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
</li>
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li id="docs-funcs-crypto"<%= sidebar_current("docs-funcs-crypto") %>>
<a href="#docs-funcs-crypto">Hash and Crypto Functions</a>
<ul class="nav nav-visible">
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-crypto-base64sha256") %>>
<a href="/docs/configuration/functions/base64sha256.html">base64sha256</a>
</li>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-crypto-base64sha512") %>>
<a href="/docs/configuration/functions/base64sha512.html">base64sha512</a>
</li>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-crypto-bcrypt") %>>
<a href="/docs/configuration/functions/bcrypt.html">bcrypt</a>
</li>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-crypto-filebase64sha256") %>>
<a href="/docs/configuration/functions/filebase64sha256.html">filebase64sha256</a>
</li>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-crypto-filebase64sha512") %>>
<a href="/docs/configuration/functions/filebase64sha512.html">filebase64sha512</a>
</li>
lang: New file-hashing functions In prior versions, we recommended using hash functions in conjunction with the file function as an idiom for detecting changes to upstream blobs without fetching and comparing the whole blob. That approach relied on us being able to return raw binary data from file(...). Since Terraform strings pass through intermediate representations that are not binary-safe (e.g. the JSON state), there was a risk of string corruption in prior versions which we have avoided for 0.12 by requiring that file(...) be used only with UTF-8 text files. The specific case of returning a string and immediately passing it into another function was not actually subject to that corruption risk, since the HIL interpreter would just pass the string through verbatim, but this is still now forbidden as a result of the stricter handling of file(...). To avoid breaking these use-cases, here we introduce variants of the hash functions a with "file" prefix that take a filename for a disk file to hash rather than hashing the given string directly. The configuration upgrade tool also now includes a rule to detect the documented idiom and rewrite it into a single function call for one of these new functions. This does cause a bit of function sprawl, but that seems preferable to introducing more complex rules for when file(...) can and cannot read binary files, making the behavior of these various functions easier to understand in isolation.
2019-01-25 18:16:43 +01:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-crypto-filemd5") %>>
<a href="/docs/configuration/functions/filemd5.html">filemd5</a>
</li>
lang: New file-hashing functions In prior versions, we recommended using hash functions in conjunction with the file function as an idiom for detecting changes to upstream blobs without fetching and comparing the whole blob. That approach relied on us being able to return raw binary data from file(...). Since Terraform strings pass through intermediate representations that are not binary-safe (e.g. the JSON state), there was a risk of string corruption in prior versions which we have avoided for 0.12 by requiring that file(...) be used only with UTF-8 text files. The specific case of returning a string and immediately passing it into another function was not actually subject to that corruption risk, since the HIL interpreter would just pass the string through verbatim, but this is still now forbidden as a result of the stricter handling of file(...). To avoid breaking these use-cases, here we introduce variants of the hash functions a with "file" prefix that take a filename for a disk file to hash rather than hashing the given string directly. The configuration upgrade tool also now includes a rule to detect the documented idiom and rewrite it into a single function call for one of these new functions. This does cause a bit of function sprawl, but that seems preferable to introducing more complex rules for when file(...) can and cannot read binary files, making the behavior of these various functions easier to understand in isolation.
2019-01-25 18:16:43 +01:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-crypto-filesha1") %>>
<a href="/docs/configuration/functions/filesha1.html">filesha1</a>
</li>
lang: New file-hashing functions In prior versions, we recommended using hash functions in conjunction with the file function as an idiom for detecting changes to upstream blobs without fetching and comparing the whole blob. That approach relied on us being able to return raw binary data from file(...). Since Terraform strings pass through intermediate representations that are not binary-safe (e.g. the JSON state), there was a risk of string corruption in prior versions which we have avoided for 0.12 by requiring that file(...) be used only with UTF-8 text files. The specific case of returning a string and immediately passing it into another function was not actually subject to that corruption risk, since the HIL interpreter would just pass the string through verbatim, but this is still now forbidden as a result of the stricter handling of file(...). To avoid breaking these use-cases, here we introduce variants of the hash functions a with "file" prefix that take a filename for a disk file to hash rather than hashing the given string directly. The configuration upgrade tool also now includes a rule to detect the documented idiom and rewrite it into a single function call for one of these new functions. This does cause a bit of function sprawl, but that seems preferable to introducing more complex rules for when file(...) can and cannot read binary files, making the behavior of these various functions easier to understand in isolation.
2019-01-25 18:16:43 +01:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-crypto-filesha256") %>>
<a href="/docs/configuration/functions/filesha256.html">filesha256</a>
</li>
lang: New file-hashing functions In prior versions, we recommended using hash functions in conjunction with the file function as an idiom for detecting changes to upstream blobs without fetching and comparing the whole blob. That approach relied on us being able to return raw binary data from file(...). Since Terraform strings pass through intermediate representations that are not binary-safe (e.g. the JSON state), there was a risk of string corruption in prior versions which we have avoided for 0.12 by requiring that file(...) be used only with UTF-8 text files. The specific case of returning a string and immediately passing it into another function was not actually subject to that corruption risk, since the HIL interpreter would just pass the string through verbatim, but this is still now forbidden as a result of the stricter handling of file(...). To avoid breaking these use-cases, here we introduce variants of the hash functions a with "file" prefix that take a filename for a disk file to hash rather than hashing the given string directly. The configuration upgrade tool also now includes a rule to detect the documented idiom and rewrite it into a single function call for one of these new functions. This does cause a bit of function sprawl, but that seems preferable to introducing more complex rules for when file(...) can and cannot read binary files, making the behavior of these various functions easier to understand in isolation.
2019-01-25 18:16:43 +01:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-crypto-filesha512") %>>
<a href="/docs/configuration/functions/filesha512.html">filesha512</a>
</li>
lang: New file-hashing functions In prior versions, we recommended using hash functions in conjunction with the file function as an idiom for detecting changes to upstream blobs without fetching and comparing the whole blob. That approach relied on us being able to return raw binary data from file(...). Since Terraform strings pass through intermediate representations that are not binary-safe (e.g. the JSON state), there was a risk of string corruption in prior versions which we have avoided for 0.12 by requiring that file(...) be used only with UTF-8 text files. The specific case of returning a string and immediately passing it into another function was not actually subject to that corruption risk, since the HIL interpreter would just pass the string through verbatim, but this is still now forbidden as a result of the stricter handling of file(...). To avoid breaking these use-cases, here we introduce variants of the hash functions a with "file" prefix that take a filename for a disk file to hash rather than hashing the given string directly. The configuration upgrade tool also now includes a rule to detect the documented idiom and rewrite it into a single function call for one of these new functions. This does cause a bit of function sprawl, but that seems preferable to introducing more complex rules for when file(...) can and cannot read binary files, making the behavior of these various functions easier to understand in isolation.
2019-01-25 18:16:43 +01:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-crypto-md5") %>>
<a href="/docs/configuration/functions/md5.html">md5</a>
</li>
lang: New file-hashing functions In prior versions, we recommended using hash functions in conjunction with the file function as an idiom for detecting changes to upstream blobs without fetching and comparing the whole blob. That approach relied on us being able to return raw binary data from file(...). Since Terraform strings pass through intermediate representations that are not binary-safe (e.g. the JSON state), there was a risk of string corruption in prior versions which we have avoided for 0.12 by requiring that file(...) be used only with UTF-8 text files. The specific case of returning a string and immediately passing it into another function was not actually subject to that corruption risk, since the HIL interpreter would just pass the string through verbatim, but this is still now forbidden as a result of the stricter handling of file(...). To avoid breaking these use-cases, here we introduce variants of the hash functions a with "file" prefix that take a filename for a disk file to hash rather than hashing the given string directly. The configuration upgrade tool also now includes a rule to detect the documented idiom and rewrite it into a single function call for one of these new functions. This does cause a bit of function sprawl, but that seems preferable to introducing more complex rules for when file(...) can and cannot read binary files, making the behavior of these various functions easier to understand in isolation.
2019-01-25 18:16:43 +01:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-crypto-rsadecrypt") %>>
<a href="/docs/configuration/functions/rsadecrypt.html">rsadecrypt</a>
</li>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-crypto-sha1") %>>
<a href="/docs/configuration/functions/sha1.html">sha1</a>
</li>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-crypto-sha256") %>>
<a href="/docs/configuration/functions/sha256.html">sha256</a>
</li>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-crypto-sha512") %>>
<a href="/docs/configuration/functions/sha512.html">sha512</a>
</li>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-crypto-uuid") %>>
<a href="/docs/configuration/functions/uuid.html">uuid</a>
</li>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
</ul>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
</li>
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li id="docs-funcs-ipnet"<%= sidebar_current("docs-funcs-ipnet") %>>
<a href="#docs-funcs-ipnet">IP Network Functions</a>
<ul class="nav nav-visible">
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-ipnet-cidrhost") %>>
<a href="/docs/configuration/functions/cidrhost.html">cidrhost</a>
</li>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-ipnet-cidrnetmask") %>>
<a href="/docs/configuration/functions/cidrnetmask.html">cidrnetmask</a>
</li>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-ipnet-cidrsubnet") %>>
<a href="/docs/configuration/functions/cidrsubnet.html">cidrsubnet</a>
</li>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
</ul>
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
</li>
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-conversion") %>>
<a href="#docs-funcs-conversion">Type Conversion Functions</a>
<ul class="nav nav-visible" id="docs-funcs-conversion">
website: Add remaining functions to the functions section sidebar These links don't lead anywhere yet.
2018-05-07 04:43:53 +02:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-conversion-tobool") %>>
<a href="/docs/configuration/functions/tobool.html">tobool</a>
</li>
lang/funcs: Type conversion functions It's not normally necessary to make explicit type conversions in Terraform because the language implicitly converts as necessary, but explicit conversions are useful in a few specialized cases: - When defining output values for a reusable module, it may be desirable to force a "cleaner" output type than would naturally arise from a computation, such as forcing a string containing digits into a number. - Our 0.12upgrade mechanism will use some of these to replace use of the undocumented, hidden type conversion functions in HIL, and force particular type interpretations in some tricky cases. - We've found that type conversion functions can be useful as _temporary_ workarounds for bugs in Terraform and in providers where implicit type conversion isn't working correctly or a type constraint isn't specified precisely enough for the automatic conversion behavior. These all follow the same convention of being named "to" followed by a short type name. Since we've had a long-standing convention of running all the words together in lowercase in function names, we stick to that here even though some of these names are quite strange, because these should be rarely-used functions anyway.
2019-01-17 18:11:48 +01:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-conversion-tolist") %>>
<a href="/docs/configuration/functions/tolist.html">tolist</a>
</li>
lang/funcs: Type conversion functions It's not normally necessary to make explicit type conversions in Terraform because the language implicitly converts as necessary, but explicit conversions are useful in a few specialized cases: - When defining output values for a reusable module, it may be desirable to force a "cleaner" output type than would naturally arise from a computation, such as forcing a string containing digits into a number. - Our 0.12upgrade mechanism will use some of these to replace use of the undocumented, hidden type conversion functions in HIL, and force particular type interpretations in some tricky cases. - We've found that type conversion functions can be useful as _temporary_ workarounds for bugs in Terraform and in providers where implicit type conversion isn't working correctly or a type constraint isn't specified precisely enough for the automatic conversion behavior. These all follow the same convention of being named "to" followed by a short type name. Since we've had a long-standing convention of running all the words together in lowercase in function names, we stick to that here even though some of these names are quite strange, because these should be rarely-used functions anyway.
2019-01-17 18:11:48 +01:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-conversion-tomap") %>>
<a href="/docs/configuration/functions/tomap.html">tomap</a>
</li>
lang/funcs: Type conversion functions It's not normally necessary to make explicit type conversions in Terraform because the language implicitly converts as necessary, but explicit conversions are useful in a few specialized cases: - When defining output values for a reusable module, it may be desirable to force a "cleaner" output type than would naturally arise from a computation, such as forcing a string containing digits into a number. - Our 0.12upgrade mechanism will use some of these to replace use of the undocumented, hidden type conversion functions in HIL, and force particular type interpretations in some tricky cases. - We've found that type conversion functions can be useful as _temporary_ workarounds for bugs in Terraform and in providers where implicit type conversion isn't working correctly or a type constraint isn't specified precisely enough for the automatic conversion behavior. These all follow the same convention of being named "to" followed by a short type name. Since we've had a long-standing convention of running all the words together in lowercase in function names, we stick to that here even though some of these names are quite strange, because these should be rarely-used functions anyway.
2019-01-17 18:11:48 +01:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-conversion-tonumber") %>>
<a href="/docs/configuration/functions/tonumber.html">tonumber</a>
</li>
lang/funcs: Type conversion functions It's not normally necessary to make explicit type conversions in Terraform because the language implicitly converts as necessary, but explicit conversions are useful in a few specialized cases: - When defining output values for a reusable module, it may be desirable to force a "cleaner" output type than would naturally arise from a computation, such as forcing a string containing digits into a number. - Our 0.12upgrade mechanism will use some of these to replace use of the undocumented, hidden type conversion functions in HIL, and force particular type interpretations in some tricky cases. - We've found that type conversion functions can be useful as _temporary_ workarounds for bugs in Terraform and in providers where implicit type conversion isn't working correctly or a type constraint isn't specified precisely enough for the automatic conversion behavior. These all follow the same convention of being named "to" followed by a short type name. Since we've had a long-standing convention of running all the words together in lowercase in function names, we stick to that here even though some of these names are quite strange, because these should be rarely-used functions anyway.
2019-01-17 18:11:48 +01:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-conversion-toset") %>>
<a href="/docs/configuration/functions/toset.html">toset</a>
</li>
lang/funcs: Type conversion functions It's not normally necessary to make explicit type conversions in Terraform because the language implicitly converts as necessary, but explicit conversions are useful in a few specialized cases: - When defining output values for a reusable module, it may be desirable to force a "cleaner" output type than would naturally arise from a computation, such as forcing a string containing digits into a number. - Our 0.12upgrade mechanism will use some of these to replace use of the undocumented, hidden type conversion functions in HIL, and force particular type interpretations in some tricky cases. - We've found that type conversion functions can be useful as _temporary_ workarounds for bugs in Terraform and in providers where implicit type conversion isn't working correctly or a type constraint isn't specified precisely enough for the automatic conversion behavior. These all follow the same convention of being named "to" followed by a short type name. Since we've had a long-standing convention of running all the words together in lowercase in function names, we stick to that here even though some of these names are quite strange, because these should be rarely-used functions anyway.
2019-01-17 18:11:48 +01:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li<%= sidebar_current("docs-funcs-conversion-tostring") %>>
<a href="/docs/configuration/functions/tostring.html">tostring</a>
</li>
lang/funcs: Type conversion functions It's not normally necessary to make explicit type conversions in Terraform because the language implicitly converts as necessary, but explicit conversions are useful in a few specialized cases: - When defining output values for a reusable module, it may be desirable to force a "cleaner" output type than would naturally arise from a computation, such as forcing a string containing digits into a number. - Our 0.12upgrade mechanism will use some of these to replace use of the undocumented, hidden type conversion functions in HIL, and force particular type interpretations in some tricky cases. - We've found that type conversion functions can be useful as _temporary_ workarounds for bugs in Terraform and in providers where implicit type conversion isn't working correctly or a type constraint isn't specified precisely enough for the automatic conversion behavior. These all follow the same convention of being named "to" followed by a short type name. Since we've had a long-standing convention of running all the words together in lowercase in function names, we stick to that here even though some of these names are quite strange, because these should be rarely-used functions anyway.
2019-01-17 18:11:48 +01:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
</ul>
lang/funcs: Type conversion functions It's not normally necessary to make explicit type conversions in Terraform because the language implicitly converts as necessary, but explicit conversions are useful in a few specialized cases: - When defining output values for a reusable module, it may be desirable to force a "cleaner" output type than would naturally arise from a computation, such as forcing a string containing digits into a number. - Our 0.12upgrade mechanism will use some of these to replace use of the undocumented, hidden type conversion functions in HIL, and force particular type interpretations in some tricky cases. - We've found that type conversion functions can be useful as _temporary_ workarounds for bugs in Terraform and in providers where implicit type conversion isn't working correctly or a type constraint isn't specified precisely enough for the automatic conversion behavior. These all follow the same convention of being named "to" followed by a short type name. Since we've had a long-standing convention of running all the words together in lowercase in function names, we stick to that here even though some of these names are quite strange, because these should be rarely-used functions anyway.
2019-01-17 18:11:48 +01:00
</li>
</ul>
</li>
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
website: Beginnings of "Functions" configuration section Previously we just listed out all of the functions in alphabetical order inside the "Interpolation Syntax" page, but that format doesn't leave much room for details and usage examples. Now we give each function its own page, and categorize them for easier navigation. While many functions are very simple and don't really warrant a full page, certain functions do have additional details that are worth mentioning and this structure scales better for those more complicated functions. So far this includes only the numeric and string functions. Other categories will follow in subsequent commits.
2018-05-07 03:32:16 +02:00
</ul>
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
</li>
</ul>
<h4>Other Docs</h4>
<ul class="nav docs-sidenav">
<li>
<a class="back" href="/downloads.html">Download Terraform</a>
</li>
website: Structural edit of configuration language docs This commit is a wide-ranging set of edits to the pages under /docs/configuration. Among other things, it - Separates style conventions out into their own page. - Separates type constraints and conversion info into their own page. - Conflates similar complex types a little more freely, since the distinction is only relevant when restricting inputs for a reusable module or resource. - Clarifies several concepts that confused me during edits.
2018-12-11 01:14:33 +01:00
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<li>
<a class="back" href="/intro/index.html">Introduction to Terraform</a>
</li>
<li>
<a class="back" href="/docs/enterprise/index.html">Terraform Enterprise</a>
</li>
<li>
<a class="back" href="/guides/index.html">Guides and Whitepapers</a>
</li>
<li>
<a class="back" href="/docs/registry/index.html">Terraform Registry</a>
</li>
<li>
<a class="back" href="/docs/github-actions/index.html">Terraform GitHub Actions</a>
</li>
<li>
<a class="back" href="/docs/extend/index.html">Extending Terraform</a>
</li>
</ul>
website: Beginnings of "Functions" configuration section Previously we just listed out all of the functions in alphabetical order inside the "Interpolation Syntax" page, but that format doesn't leave much room for details and usage examples. Now we give each function its own page, and categorize them for easier navigation. While many functions are very simple and don't really warrant a full page, certain functions do have additional details that are worth mentioning and this structure scales better for those more complicated functions. So far this includes only the numeric and string functions. Other categories will follow in subsequent commits.
2018-05-07 03:32:16 +02:00
<% end %>
website: Reorganize nav sidebars to improve jumps between sections
2018-12-21 03:18:13 +01:00
<%= yield %>
<% end %>