semaphoreio/semaphore

Show in the UI who created and last edited the secret

Open

#503 opened on Aug 19, 2025

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Elixir (77 forks)batch import
enhancementgood first issueqol

Repository metrics

Stars
 (1,519 stars)
PR merge metrics
 (Avg merge 4d 11h) (23 merged PRs in 30d)

Description

Is your improvement proposal related to a problem? Please describe.

This is a feature request to improve the secret management interface by providing more detailed information about who created and last edited a secret.

Currently, organizing and managing secrets can be challenging due to a lack of visibility into their history and usage. This makes it difficult to clean up or safely modify secrets without the risk of breaking a critical workflow.

Describe the solution you'd like

The UI element that shows details for a specific secret should be updated to include information about who created and who last updated the secret. Here is an example:

All needed information is available in the backend service and can be obtained from the front UI service via gRPC. If the secret was never updated, the update line should not be shown.

Describe alternatives you've considered

N/A

Additional context

N/A

Contributor guide

Research direction
Explore the frontend UI code to locate the secret details component. Use the existing gRPC service defined in `front/lib/internal api/secrethub.pb.ex` (lines 153-157) to fetch creator and last editor information. Modify the UI to display the 'Created by' and 'Last edited by' fields, ensuring that the update line is hidden if the secret was never updated. Refer to the mockup in the issue for layout guidance.
Tech stack
elixirgrpc
Domain
frontend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Familiarity with Semaphore's frontend codebaseBasic understanding of gRPC service calls
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75