Skip to content
This repository has been archived by the owner on Aug 1, 2024. It is now read-only.

[tracking] CDK Workshop V2 #1170

Closed
14 of 23 tasks
indrora opened this issue Sep 13, 2023 · 2 comments
Closed
14 of 23 tasks

[tracking] CDK Workshop V2 #1170

indrora opened this issue Sep 13, 2023 · 2 comments
Labels
help wanted We are asking the community to submit a PR to resolve this issue. management/tracking Issues that track a subject or multiple issues no-autoclose Exempts an issue from being closed by the stale github action. p2

Comments

@indrora
Copy link
Contributor

indrora commented Sep 13, 2023

Since there's been a lot of conversation about improvements to the CDK Workshop, let's talk about those so they dont' get lost to the sands of time.

The current outstanding updates to the current version of the CDK workshop include:

What the future of the CDK workshop looks like

I have half a mind to patch up the current content until it's "More or less correct" and make it considered the "Legacy" CDK Workshop. Take a majority of the current content, massage it down, and build it into the "Modern" CDK workshop.

This "Modern" CDK workshop would be divided into:

  • Introductory content: Deploying a very simple bucket that you can then call PutObject and ListObjects on, with associated roles and such.
  • Intermediate: Deploying a very simple container application that uses DynamoDB and some edge functions to have a page counter, built as a construct.
  • Advanced: Deploying a CI/CD pipeline, running the CDK Construct Hub
  • The Toolbox: Things that are useful to know, but don't have a "level" to them:
    • Aspects, Attributes, etc.
    • Mucking about with CloudFormation

What I want to know from the community

Given our current CDK workshop, where do you draw the lines between "intro/intermediate/advanced" topics? how would you re-design the CDK workshop today if you could?

@indrora indrora added management/tracking Issues that track a subject or multiple issues help wanted We are asking the community to submit a PR to resolve this issue. no-autoclose Exempts an issue from being closed by the stale github action. labels Sep 13, 2023
@indrora indrora pinned this issue Sep 13, 2023
@SamWSoftware
Copy link

I would add a few things for the TypeScript tutorial

  • Use the SDK V3
  • Use the NodejsFunction construct
  • Use node 20 and ideally explain what to do if a future node version comes out

I've just created a PR into the v1 cdk workshop with these changes

@kellertk kellertk unpinned this issue Aug 1, 2024
@kellertk kellertk closed this as completed Aug 1, 2024
Copy link

github-actions bot commented Aug 1, 2024

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
help wanted We are asking the community to submit a PR to resolve this issue. management/tracking Issues that track a subject or multiple issues no-autoclose Exempts an issue from being closed by the stale github action. p2
Projects
None yet
Development

No branches or pull requests

4 participants