操作配置无效:尝试读取任务定义工件文件时出现异常

kri*_*ath 5 amazon-web-services aws-codepipeline

我有一个 Codepipeline,它使用 ECS 蓝/绿部署操作将 ECR 映像部署到 ECS 集群。该管道包含两个源:一个用于使用 AWS ECR 操作的 ECR 映像,另一个用于使用第三方 Github 操作从 Github 获取配置。ECR 操作输出一个image工件,而 Github 操作输出一个config工件。这两个工件都作为 ECS 蓝/绿部署操作的输入提供。

管道在 ECS 蓝/绿部署操作中失败,并出现以下错误(从 AWS 控制台可见):

无效的操作配置

尝试从以下位置读取任务定义工件文件时出现异常:config

这是管道的结构(为了匿名而编辑了一些细节):

$ aws codepipeline get-pipeline --name my-codepipeline
{
  "pipeline": {
    "name": "my-codepipeline",
    "roleArn": "arn:aws:iam::123456789000:role/my-codepipeline-role",
    "artifactStore": {
      "type": "S3",
      "location": "my-codepipeline-s3"
    },
    "stages": [
      {
        "name": "Source",
        "actions": [
          {
            "name": "ImageSource",
            "actionTypeId": {
              "category": "Source",
              "owner": "AWS",
              "provider": "ECR",
              "version": "1"
            },
            "runOrder": 1,
            "configuration": {
              "ImageTag": "latest",
              "RepositoryName": "my-ecr"
            },
            "outputArtifacts": [
              {
                "name": "image"
              }
            ],
            "inputArtifacts": []
          },
          {
            "name": "ConfigSource",
            "actionTypeId": {
              "category": "Source",
              "owner": "ThirdParty",
              "provider": "GitHub",
              "version": "1"
            },
            "runOrder": 1,
            "configuration": {
              "Branch": "master",
              "OAuthToken": "****",
              "Owner": "me",
              "PollForSourceChanges": "false",
              "Repo": "application-config"
            },
            "outputArtifacts": [
              {
                "name": "config"
              }
            ],
            "inputArtifacts": []
          }
        ]
      },
      {
        "name": "Deploy",
        "actions": [
          {
            "name": "DeployBackend",
            "actionTypeId": {
              "category": "Deploy",
              "owner": "AWS",
              "provider": "CodeDeployToECS",
              "version": "1"
            },
            "runOrder": 1,
            "configuration": {
              "AppSpecTemplateArtifact": "config",
              "AppSpecTemplatePath": "production/appspec.yaml",
              "ApplicationName": "my-codedeploy",
              "DeploymentGroupName": "my-codedeploy-group",
              "Image1ArtifactName": "image",
              "Image1ContainerName": "IMAGE_NAME",
              "TaskDefinitionTemplateArtifact": "config",
              "TaskDefinitionTemplatePath": "production/taskdef.json"
            },
            "outputArtifacts": [],
            "inputArtifacts": [
              {
                "name": "image"
              },
              {
                "name": "config"
              }
            ]
          }
        ]
      }
    ],
    "version": 1
  },
  "metadata": {
    "pipelineArn": "arn:aws:codepipeline:ap-northeast-1:123456789000:my-codepipeline",
    "created": 1564107543.285,
    "updated": 1564107543.285
  }
}
Run Code Online (Sandbox Code Playgroud)

我检查了 S3 中的压缩工件,它肯定包含 Github 存储库中由AppSpecTemplatePath和指定的位置的配置文件TaskDefinitionTemplatePath

以下是 的内容appspec.yaml

$ cat production/appspec.yaml
version: 0.0
Resources:
  - TargetService:
      Type: AWS::ECS::Service
      Properties:
        TaskDefinition: <TASK_DEFINITION>
        LoadBalancerInfo:
          ContainerName: "my-container"
          ContainerPort: 80
Run Code Online (Sandbox Code Playgroud)

kri*_*ath 11

经过广泛尝试后,我偶然发现了一条外语线程,但我找不到它。该线程表示传递给操作的工件不能大于 3 MB。

我通过减小工件的大小解决了我的问题 ( config)。配置存储库在许多项目之间共享,通过将这些项目移动到另一个项目,我将压缩工件的大小从 14 MB 减少到 3 kB。奇迹般的是,一切都很顺利。AWS,如果您正在阅读本文,请向 ECS CodeDeploy 添加更多有关工件大小限制的文档,因为我没有看到任何有关此内容的提及,而且我无法使用这样的一般错误消息来调试此问题。

  • [本文](https://docs.aws.amazon.com/codepipeline/latest/userguide/troubleshooting.html#troubleshooting-ecstocodedeploy-size)引用了 3MB 的大小限制(不确定是否是在您发布此文章后进行的) )。 (4认同)