Closed Beta - GitLab Secrets Manager
### Overview In preparation for the launch of our GitLab Secrets Manager, this Beta release will provide an early opportunity for selected users to use a our native secrets manager in a production environment to help identify bugs or issues before launch. This Beta is our final round of planned testing before GA. ### Delivery goals [Closed experiment capabilities](https://gitlab.com/groups/gitlab-org/-/epics/14243), plus the following: - Support for self-managed. - (The appropriate) User can create, edit, and delete a secret. - Secret can be used in the CI workflow. ### Participation We are limiting the number of Beta participants, making this a closed Beta. We will be collecting feedback from participants to aid in improving the UX for GA. Interested customers should reach out through their account team to be added to the participant list. ### Note For project schedule/tracking purposes, this epic and https://gitlab.com/groups/gitlab-org/-/epics/15615 are both being previously being used to collect this body for work. The specific issues in https://gitlab.com/groups/gitlab-org/-/epics/15615 are used specifically for tracking project status and now have been moved to this epic. This epic also contains additional work which is required and tracked separately as non-critical path work. <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> > [!important] > This page may contain information related to upcoming products, features and functionality. > It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. > Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc. <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION -->
epic