ansible-collections / ansible-collections/google.cloud
Disable previous version when updating secret
- Dominant language
- Python
- Stars
- 105
- Forks
- 144
- Avg merge
- 5d 10h
- Merged PRs (30d)
- 4
Description
##### SUMMARY
When updating a secret, it could be possible to disable previous version.
##### ISSUE TYPE
- Feature Idea
##### COMPONENT NAME
gcp_secret_manager
##### ADDITIONAL INFORMATION
Avoid being able to use previous secret's versions without destroying secret.
```yaml
- name: Add a new version of a secret disabling previous one
google.cloud.gcp_secret_manager:
name: secret_key
value: updated super secret disabling previous
state: present
disable_previous_version: true
```
Contributor guide
Research direction
Start with the gcp_secret_manager component and compare its handling of secret version updates with the example playbook in the issue. Determine where a disable_previous_version option belongs, then verify that updating a secret can disable its previous version without destroying the secret.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- google-cloud, python
- Domain
- cloud, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100