aws/copilot-cli

Prompt to override previously generated pipeline files

オープン

#1,777 opened on 2020/12/22

 (3 件のコメント) (0 件のリアクション) (0 人の担当者)Go (441 件のフォーク)auto 404
good first issuesize/Stype/enhancement

Repository metrics

Stars
 (3,737 個のスター)
PR merge metrics
 (30d に merged PR はありません)

説明

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

コントリビューターガイド