aws.xxxRef Resources Creates Unneeded TF Resources For tf-aws

[hasanaburayyan]

I tried this:

bring aws;

new aws.BucketRef("blah");

wing compile -t tf-aws

THEN

tf apply

This happened:

~40 some resources are going to be made

I expected this:

No resources

Is there a workaround?

No response

Anything else?

I think this is because the ui fields we add for interacting with Refs in the simulator, and they are being turned into lambda functions in AWS

Wing Version

No response

Node.js Version

No response

Platform(s)

No response

Community Notes

• Please vote by adding a 👍 reaction to the issue to help us prioritize.
• If you are interested to work on this issue, please leave a comment.

[eladb]

Oh, seems like this is the resources used for the ui elements, no @Chriscbr ?

[Chriscbr]

Oh, seems like this is the resources used for the ui elements, no @Chriscbr ?

Yup 👍

Perhaps for now we can disable the ui elements from creating various child resources when you're compiling to non-sim targets, since Wing Console only works with simulated apps at the moment. ie

if app.target != "sim" {
  // existing logic
}

[eladb]

👍

[github-actions]

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!

[monadabot]

Congrats! 🚀 This was released in Wing 0.82.5.