BUSINESS PROBLEM
Today when you delete and/or remove a certificate with the Ansible collection, the certificate is removed from the target system but not revoked and/or soft deleted. The requires Venafi admins to perform a separate action to either revoke or place the certificate within the recycling bin, rather than it being within the same process.
PROPOSED SOLUTION
Enhance the collection to support a revocation and/or soft delete flag. This would be optional, and the action would only occur if the flag is defined. It should not be default behavior.
Example:
Set soft_delete flag to 'true'. This would move the certificate to the recycling bin and disable it when the ansible playbook is run. This would most likely be paired with a delete action on the target system.
CURRENT ALTERNATIVES
Manually revoke certificates via the Trust Protection Platform. This is an out of band process and creates more works for our Venafi admins.
BUSINESS PROBLEM Today when you delete and/or remove a certificate with the Ansible collection, the certificate is removed from the target system but not revoked and/or soft deleted. The requires Venafi admins to perform a separate action to either revoke or place the certificate within the recycling bin, rather than it being within the same process.
PROPOSED SOLUTION Enhance the collection to support a revocation and/or soft delete flag. This would be optional, and the action would only occur if the flag is defined. It should not be default behavior.
Example: Set soft_delete flag to 'true'. This would move the certificate to the recycling bin and disable it when the ansible playbook is run. This would most likely be paired with a delete action on the target system.
CURRENT ALTERNATIVES Manually revoke certificates via the Trust Protection Platform. This is an out of band process and creates more works for our Venafi admins.