Add restore and purge features for Azure secrets and keys

Created on 29 August 2021, almost 3 years ago

Updated 29 May 2024, 27 days ago

Problem/Motivation

At this stage, module is supporting only soft delete and this creates issues in multi environment setups if you accidentally delete a secret or a key as Azure won't allow to re-create the soft deleted secrets / keys with the same name until you purge it. As there is no secret / key restore feature with the module yet, this forces users to access Azure Key Vault directly to restore or purge the soft deleted secrets / keys. Goal is to provide a mechanism to let user restore a soft deleted key and / or select a key to soft delete or purge when deleting.

Proposed resolution

Appreciate any ideas / suggestions to achieve this.

I'm thinking of providing an additional checkbox in the key configuration section to set as soft delete or purge when adding / editing the key, so the key will be deleted according to the configured preference.

Not sure we can keep the entry in "Key" module when soft delete a key and introduce new operation "Restore" for soft deleted keys.

If that's possible to add more operations, we can think of adding separate operation for "Soft Delete" and use standard delete operation to "Purge" the key directly, which will allow to keep the soft deleted key still as an entry to "Restore" in a later stage.

Remaining tasks

TBA

User interface changes

TBA

API changes

TBA

Data model changes

TBA

✨ Feature request

Status

Active

Version

1.0

Component

Code

Created by

🇦🇺Australia ozwebapps Melbourne

Live updates comments and jobs are added and updated live.

Incomplete comments

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment over 1 year ago →
🇮🇹Italy apaderno Brescia, 🇮🇹
Comment 27 days ago →
🇨🇦Canada joseph.olstad
I've brought this project back from deprecation.

On friday it will have been 14 full days passed without a response from the maintainer after I contacted him offering to co-maintain. This was after more than a month of pushing up commits in issues and commenting on several important issues.

It appears that the original author/owner/maintainer of this project has won the lottery!
Comment 27 days ago →
🇨🇦Canada joseph.olstad
@ozwebapps, are you still able to review the 🌱 Offer to maintain azure_key_vault Needs review
Or have you actually won the lottery?

contrib.social Blog FAQ Discussions

Production build 0.69.0 2024