aws/copilot-cli

Prompt to override previously generated pipeline files

開放

#1,777 建立於 2020年12月22日

 (3 則留言) (0 個反應) (0 位負責人)Go (441 個分叉)auto 404
good first issuesize/Stype/enhancement

倉庫指標

星標
 (3,737 顆星)
PR 合併指標
 (30 天內沒有已合併 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

貢獻者指南