<!-- Implementation issues are used break-up a large piece of work into small, discrete tasks that can move independently through the build workflow steps. They're typically used to populate a Feature Epic. Once created, an implementation issue is usually refined in order to populate and review the implementation plan and weight. Example workflow: https://about.gitlab.com/handbook/engineering/development/threat-management/planning/diagram.html#plan --> ## Why are we doing this work See https://gitlab.com/gitlab-org/gitlab/-/issues/474432#note_2557919450. We have separate frontend and backend feature flags for the Secrets Manager. This was from when frontend started working on it first and both frontend and backend worked in parallel. There is no need to maintain both feature flags, so we can just merge them together in `secrets_manager`. This will also make it easier to manage which projects are included in the Closed Experiment and Beta. ## Relevant links https://gitlab.com/gitlab-org/gitlab/-/issues/474432+ https://gitlab.com/gitlab-org/gitlab/-/issues/427026+ (to be removed) ## Non-functional requirements - [ ] Documentation - [ ] Feature flag - [ ] Testing ## Implementation plan - [ ] Update the code to replace usage of `ci_tanukey_ui` with `secrets_manager` - [ ] Remove the feature flag and clean them up from the environments - [ ] Remove references to `ci_tanukey_ui` in the [Openbao Setup Instructions](https://gitlab.com/gitlab-org/gitlab-development-kit/-/blob/main/doc/howto/openbao.md) <!-- Workflow and other relevant labels # ~"group::" ~"Category:" ~"GitLab Ultimate" Other settings you might want to include when creating the issue. # /assign @ # /epic & --> ## Verification steps - There are no references to `ci_tanukey_ui` in the code - Pipelines should pass (all tests work as expected) and existing features are not broken