aws/copilot-cli

Prompt to override previously generated pipeline files

Aberta

#1.777 aberto em 22 de dez. de 2020

 (3 comentários) (0 reação) (0 responsável)Go (441 forks)auto 404
good first issuesize/Stype/enhancement

Métricas do repositório

Stars
 (3.737 estrelas)
Métricas de merge de PR
 (Nenhuma PRs mesclada em 30d)

Description

Hi, I'm back! I think everytime I open an issue, it's somehow related to permissions.

This time, I have successfully set up everything with copilot. For my addons, I have a template for elasticsearch and redis. I can successfully deploy it from my terminal using copilot svc deploy --name myapp --env test. Then I went to set up the pipeline next. It was going well at first, building was successful but the minute it tried to deploy, it failed.

Here is a screenshot from the console. Am I missing something? Should I have done more customization after running copilot pipeline init? Where can I add the S3 access?

This is strange because I've also already deployed a much smaller test app with crud operations on an elasticsearch addon. I was able to set up the pipeline for that too with no problem

Guia do colaborador