AWS CodePipeline Operations: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
Line 15: | Line 15: | ||
=Extended Examples= | =Extended Examples= | ||
* <span id='Simple_GitHub_-_Simulated_Shell_Build_-_Simulated_Deployment_Pipeline'></span> | * <span id='Simple_GitHub_-_Simulated_Shell_Build_-_Simulated_Deployment_Pipeline'></span>[[Simple GitHub Simulated Shell Build Simulated Deployment AWS CodePipeline Pipeline|Simple GitHub - Simulated Shell Build - Simulated Deployment Pipeline]]. | ||
=Troubleshooting and Debugging= | =Troubleshooting and Debugging= | ||
<font color=darkgray>If creating a resource that allows for a "Description", like an API Gateway API, you can use that to render various configuration parameters to be debugged: | <font color=darkgray>If creating a resource that allows for a "Description", like an API Gateway API, you can use that to render various configuration parameters to be debugged: |
Revision as of 21:50, 18 March 2019
External
Internal
Overview
Command Line Operations
Extended Examples
Troubleshooting and Debugging
If creating a resource that allows for a "Description", like an API Gateway API, you can use that to render various configuration parameters to be debugged:
AWSTemplateFormatVersion: '2010-09-09' Parameters: OpenApiAwsFile: Type: String Resources: Api: Type: AWS::ApiGateway::RestApi Properties: Name: test Description: !Sub 'This way we can render parameters ${OpenApiAwsFile}' ...