Open skorfmann opened 1 year ago
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 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!
I tried this:
specifying the
rootId
in combination withnoClean
, e.g.This happened:
the issue is, that the compile output directory differs between the two runs:
this leads to the fact, that the terraform state is not shared between the two runs and the lambda function is created twice.
I expected this:
Being able to iterate on tests without having to recreate all resources for each run.
Specifying
noClean
only would still recreate the application from scratch, that's why I thought adding therootId
flag might be helpful. I think what I actually would want is a flag likeiterate
or thenoClean
flag to behave like this.Is there a workaround?
No response
Component
CLI
Wing Version
v0.29.0
Node.js Version
18.6.0
Platform(s)
MacOS
Anything else?
No response
Community Notes