Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/terramate-io/terramate/releases below:

Releases · terramate-io/terramate · GitHub

Releases · terramate-io/terramate

• Fix ANSI escape codes that are printed to the console when running terragrunt commands with the --parallel flag.

• Fix ANSI escape codes that are printed to the console when running terragrunt commands with the --parallel flag.

• Add option --plan-render-timeout to run, and the corresponding script command option plan_render_timeout.
  • This configures the maximum time to wait (in seconds) for rendering change summaries from plan files, which will be sent to Terramate Cloud.
  • The previous default value was hardcoded at 300 seconds. In most scenarios this is more than enough,
    but there have been reported cases where rendering the changes took longer.
  • Exceeding the timeout will skip sending the change summaries, but the command status and logs are still sent.

• Fix crash in the terramate cloud login --sso command.

• Fix crash in the terramate install-completions command.
• Fix error on duplicate Terragrunt dependencies in create --all-terragrunt.
  • Duplicates are now removed and the command will no longer fail.
• Fix mistakenly detecting stacks as changed on changes in referenced Terraform modules.
  • A change in a module that is referenced by stack-a would also mark stack-aa as changed (and other stacks with a common name prefix).

• BREAKING CHANGE Massively improve stack order evaluation performance.

  This affects and improves commands that use the stack order, i.e. run, run script, list --run-order.
  As a consequence, the evaluation order of unrelated stacks may change.

  • Example 1:
    Nested stacks a must be executed after their parent stacks, but /stack1 and /stack2 are independent.

    Old run order:

    /stack1
    /stack1/a
    /stack2
    /stack2/a
    

    New run order:

    /stack1
    /stack2
    /stack1/a
    /stack2/a
    

  • Example 2:
    stack2 must be executed after stack1, but stack1 and stack3 are independent in the follwing configuration:

    /stack1 
    /stack2 (after=[stack1])
    /stack3
    

    Old run order:

    New run order:

  The new rule recursively aligns stacks that are independent into groups.

  • The first group contains all initially independent stacks.
  • The second group contains all stacks that just depended on stacks in the first group.
  • The third group contains all stacks that just depended on stacks in both previous groups.
  • The fourth group and following groups continue in the same way.

  Stacks in each group are ordered lexicographically and returned as the order of execution when running sequentially.

  The run order when using the --parallel flag is not affected by this change.

• (BREAKING CHANGE) Improve stack order evaluation performance.
  This affects commands that use the stack order, i.e. run, run script, list --run-order.
  As a consequence, the evaluation order of unrelated stacks may change.

  • Example 1

    /stack1
    /stack1/a
    /stack2
    /stack2/a
    

    Sub-stacks a must be executed after their parent stacks, but /stack1 and /stack2 are unrelated.

    Old run order:

      /stack1
      /stack1/a
      /stack2
      /stack2/a
    

    New run order:

      /stack1
      /stack2
      /stack1/a
      /stack2/a
    

  • Example 2

    /stack1 
    /stack2 (after=[stack1])
    /stack3
    

    stack2 must be executed after stack1, but stack3 is unrelated.

    Old run order:

    New run order:

  The new rule first runs stacks that have no dependencies in group 1,
  then those in group 2 that depend on stacks in group 1,
  then those in group 3 that depend on stacks in group 1 and group 2, and so on.
  Stacks in each group are ordered lexicographically.

  The run order when using the --parallel flag is not affected by this.

• Support tag:<query> selectors in stack attributes wants and wanted_by.
• Add support for creating previews and detecting merge request metadata in Gitlab merged results pipelines.

• Upgrade dependency github.com/cli/go-gh/v2 from v2.11.1 to v2.12.1.
  • Previous version had vulnerabilities that did not affect terramate, but would show up in security reports.

• Parallel loading of Terragrunt modules.

• Fix Terragrunt integration not skipping hidden directories and not honoring .tmskip file.

You can’t perform that action at this time.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4