GitHub Authentication for AWS CodePipeline: Difference between revisions
Jump to navigation
Jump to search
| Line 17: | Line 17: | ||
Use the procedure described here: {{Internal|GitHub_Procedures#Create_a_Personal_Access_Token_for_Command_Line|Create a GitHub Personal Access Token}} | Use the procedure described here: {{Internal|GitHub_Procedures#Create_a_Personal_Access_Token_for_Command_Line|Create a GitHub Personal Access Token}} | ||
==Update the Pipeline== | |||
===CloudFormation=== | |||
===AWS CLI=== | |||
<font color=darkgray>TODO, not tested.</font> | |||
aws codepipeline get-pipeline --name MyPipeline > pipeline.json | |||
Update pipeline.json, as described [[#CloudFormation|above]], then | |||
aws codepipeline update-pipeline --cli-input-json file://pipeline.json | |||
Revision as of 22:53, 13 March 2019
External
Internal
Overview
This article describes how to configure the Source stage of an AWS CodePipeline to access a GitHub repository.
Procedure
Create a Personal Access Token
Use the procedure described here:
Update the Pipeline
CloudFormation
AWS CLI
TODO, not tested.
aws codepipeline get-pipeline --name MyPipeline > pipeline.json
Update pipeline.json, as described above, then
aws codepipeline update-pipeline --cli-input-json file://pipeline.json