Reposted by cdk.dev
Just using AWS Console-to-Code for new IAC code :)
aws.amazon.com/blogs/aws/co...
#ClickOps #AWS #IAC #CDK
aws.amazon.com/blogs/aws/co...
#ClickOps #AWS #IAC #CDK
Convert AWS console actions to reusable code with AWS Console-to-Code, now generally available | Amazon Web Services
AWS Console-to-Code generates reusable infrastructure as code from your AWS console actions, supporting Amazon EC2, RDS, and VPC. With a few clicks, get CloudFormation, CDK (TypeScript, Python, Java),...
aws.amazon.com
March 20, 2025 at 10:13 AM
Just using AWS Console-to-Code for new IAC code :)
aws.amazon.com/blogs/aws/co...
#ClickOps #AWS #IAC #CDK
aws.amazon.com/blogs/aws/co...
#ClickOps #AWS #IAC #CDK
Reposted by cdk.dev
Empower developers with EventCatalog MCP Server
YouTube video by EventCatalog
www.youtube.com
March 18, 2025 at 1:26 PM
Reposted by cdk.dev
My typical workflow is:
• Checkout main branch
• cdk diff → no changes (supposed to be)
• Make changes on branch
• CDK Diff should only show the changes you did
Doing this locally is not always possible. If it is not make use of it in PR comments or in the build pipeline.
• Checkout main branch
• cdk diff → no changes (supposed to be)
• Make changes on branch
• CDK Diff should only show the changes you did
Doing this locally is not always possible. If it is not make use of it in PR comments or in the build pipeline.
March 6, 2025 at 5:07 AM
My typical workflow is:
• Checkout main branch
• cdk diff → no changes (supposed to be)
• Make changes on branch
• CDK Diff should only show the changes you did
Doing this locally is not always possible. If it is not make use of it in PR comments or in the build pipeline.
• Checkout main branch
• cdk diff → no changes (supposed to be)
• Make changes on branch
• CDK Diff should only show the changes you did
Doing this locally is not always possible. If it is not make use of it in PR comments or in the build pipeline.