Skip to content

cidr_blocks outputs for unused features result in diff after apply #743

@lorengordon

Description

@lorengordon

There is some kind of issue going on with the cidr_blocks outputs for unused features. After first apply, they are lists of nulls, but the second apply they are reported as a planned change, becoming lists of empty strings...

This was tested on the latest matter branch in the complete-vpc example.

Changes to Outputs:
  ~ database_subnets_ipv6_cidr_blocks    = [
      - null,
      - null,
      - null,
      + "",
      + "",
      + "",
    ]
  ~ elasticache_subnets_ipv6_cidr_blocks = [
      - null,
      - null,
      - null,
      + "",
      + "",
      + "",
    ]
  ~ intra_subnets_ipv6_cidr_blocks       = [
      - null,
      - null,
      - null,
      + "",
      + "",
      + "",
    ]
  ~ private_subnets_ipv6_cidr_blocks     = [
      - null,
      - null,
      - null,
      + "",
      + "",
      + "",
    ]
  ~ public_subnets_ipv6_cidr_blocks      = [
      - null,
      - null,
      - null,
      + "",
      + "",
      + "",
    ]
  ~ redshift_subnets_ipv6_cidr_blocks    = [
      - null,
      - null,
      - null,
      + "",
      + "",
      + "",
    ]

You can apply this plan to save these new output values to the Terraform state, without changing any real infrastructure.

Originally posted by @lorengordon in #737 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions