如何使用CircleCI的ecs orbs来执行depends_on的实际工作票务。

huangapple
go评论89阅读模式
英文:

How to use CircleCI's ecs orbs to do actual ticketing of depends_on

问题

以下是翻译好的部分：

我目前正在使用 CircleCI 和 ECS orbs 进行部署。

这是 config.yaml 的内容：

  1. version: 2.1
  3. orbs:
  4.   aws-ecr: circleci/aws-ecr@8.2.1
  5.   aws-ecs: circleci/aws-ecs@3.2.0
  7. jobs:
  8.   dev-ecr-push-go-image:
  9.     executor: aws-ecr/default
  10.     steps:
  12. workflows:
  13.   ci_workflow:
  14.     jobs:
  15.     - aws-ecr/build-and-push-image:
  16.         name: dev-ecr-push-go-image
  17.         registry-id: DEV_AWS_ECR_REGISTRY_ID
  18.         aws-access-key-id: DEV_AWS_ACCESS_KEY_ID
  19.         aws-secret-access-key: DEV_AWS_SECRET_ACCESS_KEY
  20.         public-registry: false
  21.         push-image: true
  22.         dockerfile: ./docker/deploy/go/Dockerfile
  23.         repo: 'development/app'
  24.         tag: '${CIRCLE_SHA1}'
  26.     - aws-ecr/build-and-push-image:
  27.         name: dev-ecr-push-nginx-image
  28.         registry-id: DEV_AWS_ECR_REGISTRY_ID
  29.         aws-access-key-id: DEV_AWS_ACCESS_KEY_ID
  30.         aws-secret-access-key: DEV_AWS_SECRET_ACCESS_KEY
  31.         public-registry: false
  32.         push-image: true
  33.         dockerfile: ./docker/deploy/nginx/Dockerfile
  34.         repo: 'development/nginx'
  35.         tag: '${CIRCLE_SHA1}'
  37.     - aws-ecs/deploy-service-update:
  38.         name: dev-ecs-deploy
  39.         aws-access-key-id: DEV_AWS_ACCESS_KEY_ID
  40.         aws-secret-access-key: DEV_AWS_SECRET_ACCESS_KEY
  41.         cluster: 'development'
  42.         container-image-name-updates: 'container=nginx,tag=${CIRCLE_SHA1},container=app,tag=${CIRCLE_SHA1}'
  43.         family: 'development'
  44.         service-name: 'development'
  45.         requires:
  46.         - dev-ecr-push-go-image
  47.         - dev-ecr-push-nginx-image

当我创建一个任务时，我希望在启动 go 容器后启动 nginx 容器。这可以很容易地通过使用 docker-compose 实现，我已确认它也可以在 ECS 任务定义上实现。您可以参考以下链接：https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definition_parameters.html

但是，在 CircleCI 中实现 dependsOn 的最佳方法是什么？我查看了 orbs 文档，但没有找到解决方案。您可以参考以下链接：https://circleci.com/developer/ja/orbs/orb/circleci/aws-ecs

英文:

I am currently deploying with CircleCI using ECS orbs.

Here are the contents of config.yaml.

  1. version: 2.1
  3. orbs:
  4.   aws-ecr: circleci/aws-ecr@8.2.1
  5.   aws-ecs: circleci/aws-ecs@3.2.0
  8. jobs:
  9.   dev-ecr-push-go-image:
  10.     executor: aws-ecr/default
  11.     steps:
  14. workflows:
  15.   ci_workflow:
  16.     jobs:
  17.     - aws-ecr/build-and-push-image:
  18. 　　　　　　　　　　　　　　　　name: dev-ecr-push-go-image
  19.         registry-id: DEV_AWS_ECR_REGISTRY_ID
  20.         aws-access-key-id: DEV_AWS_ACCESS_KEY_ID
  21.         aws-secret-access-key: DEV_AWS_SECRET_ACCESS_KEY
  22.         public-registry: false
  23.         push-image: true
  24.         dockerfile: ./docker/deploy/go/Dockerfile
  25.         repo: 'development/app'
  26.         tag: '${CIRCLE_SHA1}'
  28.     - aws-ecr/build-and-push-image:
  29.         name: dev-ecr-push-nginx-image
  30.         registry-id: DEV_AWS_ECR_REGISTRY_ID
  31.         aws-access-key-id: DEV_AWS_ACCESS_KEY_ID
  32.         aws-secret-access-key: DEV_AWS_SECRET_ACCESS_KEY
  33.         public-registry: false
  34.         push-image: true
  35.         dockerfile: ./docker/deploy/nginx/Dockerfile
  36.         repo: 'development/nginx'
  37.         tag: '${CIRCLE_SHA1}'
  38.     - aws-ecs/deploy-service-update:
  39.         name: dev-ecs-deploy
  40.         aws-access-key-id: DEV_AWS_ACCESS_KEY_ID
  41.         aws-secret-access-key: DEV_AWS_SECRET_ACCESS_KEY
  42.         cluster: 'development'
  43.         container-image-name-updates: 'container=nginx,tag=${CIRCLE_SHA1},container=app,tag=${CIRCLE_SHA1}'
  44.         family: 'development'
  45.         service-name: 'development'
  46.         requires:
  47.         - dev-ecr-push-go-image
  48.         - dev-ecr-push-nginx-image
  49.

When I create a task, I want the nginx container to be started after the go container is started.
This can be done easily with docker-compose, and I have confirmed that it can also be done with task definitions on the ECS side.
https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definition_parameters.html

But what is the best way to achieve dependsOn with CircleCI?
I checked the orbs documentation but could not find a solution.
https://circleci.com/developer/ja/orbs/orb/circleci/aws-ecs

答案1

得分: 0

以下是您要翻译的内容：

这是我的task_definition.json中的配置错误。
我忘记设置要与“links”一起启动的容器的顺序。

英文:

It was a configuration error in my task_definition.json.
I forgot to set the order of containers to be launched with "links".

huangapple
  • 本文由 发表于 2023年7月13日 12:49:01
  • 转载请务必保留本文链接：https://go.coder-hub.com/76676022.html
  • amazon-web-services
  • circleci
  • docker
匿名

发表评论

匿名网友

:?: :razz: :sad: :evil: :!: :smile: :oops: :grin: :eek: :shock: :???: :cool: :lol: :mad: :twisted: :roll: :wink: :idea: :arrow: :neutral: :cry: :mrgreen:

确定