iam_user: permissions_boundary attribute should accept empty string as absent value

[mgarstecki]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Same as #5546, which was for roles : accepting an empty string would allow designing modules that take a permissions boundary as optional input.

PR in progress.

New or Affected Resource(s)

• aws_iam_user

Potential Terraform Configuration

variable "permissions_boundary_arn" {
  default = ""
}

resource "aws_iam_user" "test-user" {
  name = "mat-test-user-boundary"
  permissions_boundary = "${var.permissions_boundary_arn}"
}

The above topology fails for the default value of permissions_boundary_arn, making it hard to design a module that fits both privileged users (who don't need to provide a boundary) and limited ones (who need to provide one).

References

• iam_role: permissions_boundary attribute should accept empty string as absent value #5546: the same, but for roles.

[bflad]

This has been merged into master and will release with version 1.36.0 of the AWS provider, likely very shortly. 👍

[bflad]

This has been released in version 1.36.0 of the AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!