The AWS CDK - The Bad Parts

Поделиться
HTML-код
  • Опубликовано: 8 ноя 2024

Комментарии • 11

  • @luiscarlosjayk
    @luiscarlosjayk Год назад

    Along with the *Semantic Versioning* issue is the fact that documentation also falls behind the actual implementation.
    I've found myself into troubles doing workarounds because the expected properties for a constructor or method from the documentation are not supported anymore, and only way I realize is when I check the type definitions in cdk source code.

  • @GovindKumar-qi5dd
    @GovindKumar-qi5dd 2 года назад +2

    BROTHER, YOU ARE THE BEST!!! You oooh really helped me!! THANK YOU VERY

  • @devops-sushi5534
    @devops-sushi5534 6 месяцев назад

    Is there a good solution of creating multiple bootstraps for different projects, each with their won deployment OIDC role (policies)? [in the same aws account]

    • @MatthewBonig
      @MatthewBonig  4 месяца назад

      This is possible but hard to document in YT comments,

  • @moisesyatnielgabarretehern2814
    @moisesyatnielgabarretehern2814 2 года назад +1

    This helped a lot thank you

  • @user-dl7mn3ti9u
    @user-dl7mn3ti9u 2 года назад +1

    Finally a working method

  • @fmikael1
    @fmikael1 Год назад +1

    CDK has frustrated me quite a bit - in particular getting a cross account CodeCommit repository hooked up. You know it's bad when it's easier to integrate third party repositories than it is with your own proprietary products. Sorry just had to rant

  • @brandondixon6333
    @brandondixon6333 2 года назад

    I just want someone to solve the EC2 instance profile issue so I can spin up multiple EC2 instances with the same IAM role but it not create each one a separate instance profile.

    • @MatthewBonig
      @MatthewBonig  2 года назад

      Come ask the question in the cdk.dev Slack server