Align Vault Usage Teams

Developers are asking more and more about how to use secrets as the dev portal documentation is not enough and do not address all different usecases for different environments and product types. They know what they need to do for development, experimentation, integration, staging and production regarding secrets with detailed how-to and reference documentation

Also IaC secrets have been organically developed to follow the repository layouts but there are non-used, deprecated, invalid secrets and secret engines that causes duplication and confusion so they need to be cleaned up to follow the latest config management guideliness.

• Improve secret management usage documentations to handle below scenarios and mention any discrepancies as needed between datacentres
  • A developer wants to use their own secrets while developing
  • A developer wants to share team secrets while developing
  • A team wants to use secrets in their own CI/CD/Integration testing
  • A team wants to share secrets with a different team
  • A team wants to push/create/trigger secrets for staging/production environments
• Provide a reference implementation in an example repository