Skip to content

Conversation

@tbarthel-fr
Copy link

This commit introduces a write-only password feature to the onepassword_item resource. This allows for setting a password that is not stored in the Terraform state, which is useful for ephemeral values.

The following new attributes have been added:

  • password_wo: A write-only password.
  • password_wo_version: An integer that must be incremented to trigger an update to the password_wo field.

This commit also includes:

  • Updates to various Go dependencies, including the Terraform plugin framework so that schema.StringAttribute.WriteOnly can be used.
  • New acceptance tests for the write-only password functionality.

This commit introduces a write-only password feature to the `onepassword_item` resource. This allows for setting a password that is not stored in the Terraform state, which is useful for ephemeral
values.

The following new attributes have been added:
- `password_wo`: A write-only password.
- `password_wo_version`: An integer that must be incremented to trigger an update to the `password_wo` field.

This commit also includes:
- Updates to various Go dependencies, including the Terraform plugin framework so that `schema.StringAttribute.WriteOnly` can be used.
- New acceptance tests for the write-only password functionality.
# Conflicts:
#	go.mod
#	go.sum
#	internal/provider/const.go
#	internal/provider/onepassword_item_resource_test.go
Copy link
Contributor

@volodymyrZotov volodymyrZotov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tbarthel-fr Thank you for the contribution!

I was able to review it and found that if using password_wo it still stored raw password in the plan.

To reproduce,

  1. terraform plan -out=tfplan
  2. terraform show -json tfplan | jq (skip jq if you don ot have it)
  3. Check printed plan and see that password still have a value.

Could you please take a look into that?

MarkdownDescription: passwordWriteOnceDescription,
Optional: true,
Sensitive: true,
WriteOnly: true,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

WriteOnly property not exists here.

@volodymyrZotov volodymyrZotov added the blocked Work cannot proceed due to an external or internal dependency. label Dec 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

blocked Work cannot proceed due to an external or internal dependency. enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants