Maintenance: Remove cloud development environment configurations (Gitpod, Codespaces, devcontainer)

[leandrodamascena]

Why is this needed?

1. Low/unknown usage: There's no indication that contributors are actively using these cloud environments, and no way to measure adoption

2. Shift in developer workflows: The rise of AI-assisted local development tools has reduced the need for pre-configured cloud environments—developers can now get help setting up local environments and navigating unfamiliar codebases more easily

3. Maintenance overhead: These configurations require ongoing maintenance (Node.js versions, base images, VS Code extensions, SAM CLI updates) without clear value to the project

4. Gitpod sunset: Gitpod Classic is being discontinued in October 2025, making those references obsolete regardless

5. Simple local setup: The repository already provides npm run setup-local which handles environment bootstrapping—the barrier to local contribution is already low

Which area does this relate to?

No response

Solution

Remove all cloud-based development environment configurations from the repository, including Gitpod references and the devcontainer setup used by GitHub Codespaces. This includes updating the contributing guidelines in both the main repository and documentation site.

Background on Gitpod: Gitpod Classic (pay-as-you-go) is being sunset on October 15, 2025, as announced in the official Gitpod GitHub repository.

Files to be updated:

• CONTRIBUTING.md - Remove Gitpod and GitHub Codespaces sections, keep only local environment setup
• docs/contributing/setup.md - Remove Gitpod and GitHub Codespaces sections, remove cloud pricing warning

Acknowledgment

• This request meets Powertools for AWS Lambda (Python) Tenets
• Should this be considered in other Powertools for AWS Lambda languages? i.e. Java, TypeScript, and .NET

[powertools-for-aws-oss-automation]

Warning

This issue is now closed. Please be mindful that future comments are hard for our team to see.
If you need more assistance, please either reopen the issue, or open a new issue referencing this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

[github-actions]

This is now released under 3.24.0 version!