output of plan is not human-readable

[rblumen-desk]

Hi there,

Terraform Version

v0.12.24

Affected Resource(s)

Please list the resources as a list, for example:

• pagerduty_team_membership
• pagerduty_schedule

Feature request

The terraform plan output currently shows the internal pagerduty IDs for users
e.g.

  + resource "pagerduty_team_membership" "membership" {
      + id      = (known after apply)
      + team_id = "PxxxxxB"
      + user_id = "PxxxxxY"
    }

  ~ resource "pagerduty_schedule" "tier_1_on_call" {
[...]
      ~ layer {
     
           users                        = [
[...]
                "P.....K",
                "P.....D",
            ]
        }
    }

The purpose of the plan is to determine whether or not to apply. It would be helpful if the plan used the human-readable names for objects rather than the internal ids.

[stmcallister]

hi @rblumen-desk! Thanks for the feedback! Have you seen this kind of behavior in other providers, where the plan shows information that is not going to be passed back to the API?

[rblumen-desk]

@stmcallister other providers that I have used show both internal machine-readable keys and human-readable information. In the terraform development cycle, the purpose of the plan phase is so that a developer can determine whether to run apply to make the changes permanent so a human readable output makes that more straightforward.