KusionStack/kusion

Feat: Support SetSecret via secret store interface

Open

#1,411 opened on Feb 12, 2025

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)Go (108 forks)auto 404
help wantedkind/feature

Repository metrics

Stars
 (1,315 stars)
PR merge metrics
 (PR metrics pending)

Description

What would you like to be added?

Currently Kusion defines the secret store interface with only a GetSecret() method. See: https://github.com/KusionStack/kusion/blob/main/pkg/secrets/interfaces.go

Add a SetSecret() method for the interface and support it in all implementations (aws/azure/gcp/alicloud/viettel).

Why is this needed?

Writing a secret to a secret store may be used when:

  • Storing sensitive information in variable sets
  • Storing kubeconfig to be used by the Kubernetes runtime (#1409)

Tasks

  • Add interface of GetSecret #1433
  • Implement GetSecret in Alicloud Secretmanager
  • Implement GetSecret in AWS Secretmanager
  • Implement GetSecret in Azure SecretManager
  • Implement GetSecret in Hashicorp Vault SecretManager
  • Implement GetSecret in Viettelcloud Secretmanager

Contributor guide

Research direction
Study the existing secret store interface and the GetSecret implementation pattern. Then add SetSecret to the interface and implement it for each provider (AWS, Azure, GCP, Alicloud, Viettel, Hashicorp Vault). Follow the same error handling and struct patterns as GetSecret.
Tech stack
go
Domain
backendapidevops
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GoLinux
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60