Skip to content
This repository has been archived by the owner on Feb 16, 2023. It is now read-only.

Remove secret at old path when secret path is updated #120

Merged
merged 1 commit into from
Jan 25, 2021

Conversation

SimonBarendse
Copy link
Member

Previously, when updating the path of a secrethub_secret resource the secret would be created in the new location, but the secret would also remain at the old location. This commit changes the behavior so that the secret is removed in the old location when the path of the secret resource is changed.

Previously, when updating the path of a secrethub_secret resource
the secret would be created in the new location, but the secret
would also remain at the old location. This commit changes the
behavior so that the secret is removed in the old location when
the path of the secret resource is changed.
@SimonBarendse SimonBarendse added the bug Something isn't working label Jan 6, 2021
Copy link
Member

@florisvdg florisvdg left a comment

Choose a reason for hiding this comment

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

Yep, we can indeed now do this, unlike before, because the provider path_prefix has been removed.

@SimonBarendse SimonBarendse merged commit 78c3814 into develop Jan 25, 2021
@SimonBarendse SimonBarendse deleted the fix/secret-path-change branch January 25, 2021 11:14
@florisvdg florisvdg mentioned this pull request Feb 9, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants