Open ShaiBer opened 10 months ago
I'd emphasize engine-agnosticness, not just aws cdk.
Hi,
This issue hasn't seen activity in 60 days. Therefore, we are marking this issue as stale for now. It will be closed after 7 days. Feel free to re-open this issue when there's an update or relevant information to be added. Thanks!
Hi,
This issue hasn't seen activity in 90 days. Therefore, we are marking this issue as stale for now. It will be closed after 7 days. Feel free to re-open this issue when there's an update or relevant information to be added. Thanks!
Hi,
This issue hasn't seen activity in 90 days. Therefore, we are marking this issue as stale for now. It will be closed after 7 days. Feel free to re-open this issue when there's an update or relevant information to be added. Thanks!
Feature Spec
Anyone who skims through our docs doesn't get the impression that we are a Terraform shop only, especially when reading the getting started guild - https://www.winglang.io/docs/start-here/aws
Use Cases
We are losing potential users coming from the CDK that don't see we compile to the CDK. It also creates concern that we have a risk related to the new TF licensing
Implementation Notes
We only give Terraform (or TF) as the compilation artifact throughout our docs. We should change this. Easiest thing would probably be to start by searching "Terraform" and "TF". In the getting started guide, in the "Deploy to AWS" section, it also only shows how to deploy with TF (https://www.winglang.io/docs/start-here/aws).
We also give this impression on our websites.
Component
Documentation
Community Notes