aws/copilot-cli

Show warning message before deployment when a secret does not exist

Open

#5,662 opened on Feb 8, 2024

View on GitHub
 (1 comment) (7 reactions) (0 assignees)Go (3,737 stars) (441 forks)auto 404
good first issuetype/enhancement

Description

Currently when you specify a non-existing secret in the service manifest and make a deployment, you won't get any error message until the ECS keeps failing to create any stable task, and it takes quite long time for rollback to complete. It would be nice if Copilot can validate the existence for the secrets specified and give a warning or error out if any of them does not exist.

Contributor guide

Tech stack
go
Domain
backend
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.
half day
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.
clear
Prerequisites
GitGoAWS account
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Explore how the Copilot CLI currently parses service manifests and retrieves secrets. Understand the deployment flow and locate where secret validation could be added. Look at existing AWS Secrets Manager API calls in the codebase.