Skip to content

Latest commit

 

History

History
92 lines (53 loc) · 1.62 KB

UPGRADE-5.0.md

File metadata and controls

92 lines (53 loc) · 1.62 KB

Upgrade from v4.x to v5.x

Please consult the examples directory for reference example configurations. If you find a bug, please open an issue with supporting configuration to reproduce.

⚠️ This guide is under active development. As tasks for v5.0 are implemented, the associated upgrade guidance/changes are documented here. See here to track progress of v5.0 implementation.

List of backwards incompatible changes

Additional changes

Added

Modified

Removed

Variable and output changes

  1. Removed variables:

  2. Renamed variables:

  3. Added variables:

  4. Removed outputs:

  5. Renamed outputs:

  6. Added outputs:

Upgrade Migrations

Before - v4.x Example

module "eks_blueprints" {
  source = "github.com/aws-ia/terraform-aws-eks-blueprints?ref=v4.4.0"

  # TODO

}

After - v5.x Example

module "eks_blueprints" {
  source = "github.com/aws-ia/terraform-aws-eks-blueprints?ref=v5.0.0"

  # TODO

}

Diff of Before vs After

module "eks_blueprints" {
-  source = "github.com/aws-ia/terraform-aws-eks-blueprints?ref=v4.4.0"
+  source = "github.com/aws-ia/terraform-aws-eks-blueprints?ref=v5.0.0"

  # TODO
}

State Move Commands

In conjunction with the changes above, users can elect to move their external capacity provider(s) under this module using the following move command. Command is shown using the values from the example shown above, please update to suit your configuration names:

terraform state mv 'xxx' 'yyy'