Skip to content

configure_user module forces actions on every apply due to timestamp() trigger #185

@donpellegrino

Description

@donpellegrino

Affected modules

  • configure_user

Terraform CLI and Terraform provider versions

$ terraform -v
Terraform v1.13.4
on linux_amd64

  • provider registry.terraform.io/hashicorp/null v3.2.4
  • provider registry.terraform.io/hashicorp/time v0.13.1
  • provider registry.terraform.io/ibm-cloud/ibm v1.84.3
  • provider registry.terraform.io/mastercard/restapi v2.0.1

Expected behavior

After a successful terraform apply subsequent runs of terraform apply should not have any changes to make.

Actual behavior

The configure_user submodule unconditionally runs on every terraform apply due to using timestamp() as a trigger, violating Terraform's core principle that infrastructure matching configuration should show no changes in plan.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions