AWS中的CodePipeline在蓝绿部署中有效,但是GitHub文件未在服务器上。
创始人
2024-09-28 02:31:16
0

在AWS中使用CodePipeline进行蓝绿部署时,确保在部署过程中将GitHub文件同步到服务器上,可以按照以下步骤进行操作:

  1. 在AWS控制台中打开CodePipeline服务。
  2. 创建或编辑一个CodePipeline流水线,确保已经添加了适当的源和目标阶段。
  3. 在部署阶段中,确保选择了适当的部署提供程序,例如AWS Elastic Beanstalk或AWS CodeDeploy。
  4. 在部署提供程序中配置部署操作,确保在部署过程中将GitHub文件同步到服务器上。

下面是一个示例的CloudFormation模板,用于在部署过程中将GitHub文件同步到AWS Elastic Beanstalk上:

Resources:
  MyApplication:
    Type: AWS::ElasticBeanstalk::Application
    Properties:
      ApplicationName: MyApplication

  MyEnvironment:
    Type: AWS::ElasticBeanstalk::Environment
    Properties:
      ApplicationName: !Ref MyApplication
      EnvironmentName: MyEnvironment
      SolutionStackName: "64bit Amazon Linux 2018.03 v2.14.5 running Node.js"
      OptionSettings:
        - Namespace: aws:elasticbeanstalk:application:sourcebundle
          OptionName: S3Bucket
          Value: !Ref S3Bucket
        - Namespace: aws:elasticbeanstalk:application:sourcebundle
          OptionName: S3Key
          Value: !Ref S3Key

  MyPipeline:
    Type: AWS::CodePipeline::Pipeline
    Properties:
      Name: MyPipeline
      RoleArn: !GetAtt PipelineRole.Arn
      ArtifactStore:
        Type: S3
        Location: !Ref S3Bucket
      Stages:
        - Name: Source
          Actions:
            - Name: SourceAction
              ActionTypeId:
                Category: Source
                Owner: ThirdParty
                Provider: GitHub
                Version: 1
              Configuration:
                Owner: owner-name
                Repo: repo-name
                Branch: branch-name
                OAuthToken: !Ref GitHubToken
              OutputArtifacts:
                - Name: SourceOutput
              RunOrder: 1
        - Name: Build
          Actions:
            - Name: BuildAction
              ActionTypeId:
                Category: Build
                Owner: AWS
                Provider: CodeBuild
                Version: 1
              Configuration:
                ProjectName: !Ref CodeBuildProject
              InputArtifacts:
                - Name: SourceOutput
              OutputArtifacts:
                - Name: BuildOutput
              RunOrder: 2
        - Name: Deploy
          Actions:
            - Name: DeployAction
              ActionTypeId:
                Category: Deploy
                Owner: AWS
                Provider: ElasticBeanstalk
                Version: 1
              Configuration:
                ApplicationName: !Ref MyApplication
                EnvironmentName: !Ref MyEnvironment
              InputArtifacts:
                - Name: BuildOutput
              RunOrder: 3

  PipelineRole:
    Type: AWS::IAM::Role
    Properties:
      AssumeRolePolicyDocument:
        Version: "2012-10-17"
        Statement:
          - Effect: Allow
            Principal:
              Service: codepipeline.amazonaws.com
            Action: sts:AssumeRole
      Policies:
        - PolicyName: MyPipelinePolicy
          PolicyDocument:
            Version: "2012-10-17"
            Statement:
              - Effect: Allow
                Action:
                  - elasticbeanstalk:CreateApplicationVersion
                  - elasticbeanstalk:UpdateEnvironment
                Resource:
                  - !Sub arn:aws:elasticbeanstalk:${AWS::Region}:${AWS::AccountId}:application/MyApplication
                  - !Sub arn:aws:elasticbeanstalk:${AWS::Region}:${AWS::AccountId}:environment/MyApplication/MyEnvironment
              - Effect: Allow
                Action:
                  - codebuild:StartBuild
                Resource:
                  - !Sub arn:aws:codebuild:${AWS::Region}:${AWS::AccountId}:project/MyCodeBuildProject
              - Effect: Allow
                Action:
                  - s3:GetObject
                  - s3:PutObject
                Resource:
                  - !Sub arn:aws:s3:::${S3Bucket}/*

在上述示例中,我们使用了一个名为MyPipeline的CodePipeline流水线,它包含了三个阶段:Source、Build和Deploy。在Source阶段中,我们使用了GitHub提供的ActionTypeId,配置

相关内容

热门资讯

科技通报!佛手在线大菠萝辅助(... 科技通报!佛手在线大菠萝辅助(辅助挂)真是存在有挂(确实有挂辅助器)1、上手简单,内置详细流程视频教...
玩家攻略!cloudpoker... 玩家攻略!cloudpoker作弊(辅助挂)真是是真的有挂(有挂技术辅助软件)1、进入到是否有挂之后...
科技通报!wpk可以作弊吗(辅... 科技通报!wpk可以作弊吗(辅助挂)真是有挂(有挂解密辅助软件)1、起透看视 辅助软件价格2、随意选...
发现玩家!htx矩阵wepok... 发现玩家!htx矩阵wepoker辅助(辅助挂)其实存在有挂(有挂规律辅助方法)1)免费钻石:进一步...
分享一款!hhpoker脚本(... 分享一款!hhpoker脚本(辅助挂)好像是有挂(有挂秘籍辅助脚本)1、起透看视 辅助软件价格2、随...
科技新动态!wepoker辅助... 科技新动态!wepoker辅助插件功能(辅助挂)其实真的是有挂(揭秘有挂辅助工具)1、实时透视辅助更...
一分钟了解!约局吧德州真的有透... 一分钟了解!约局吧德州真的有透视挂吗(辅助挂)真是真的是有挂(真的有挂辅助插件)1、一分钟了解!约局...
实测教程!wpk安卓下载辅助(... 实测教程!wpk安卓下载辅助(辅助挂)真是有挂(有挂功能辅助器)1、起透看视 辅助软件价格2、随意选...
玩家必备教程!aapoker能... 玩家必备教程!aapoker能控制牌吗(辅助挂)一直真的有挂(有挂细节辅助技巧)1、首先打开辅助器下...
玩家科普!wepoker辅助器... 玩家科普!wepoker辅助器(辅助挂)好像真的是有挂(有挂透视辅助方法)1、用户打开应用后不用登录...