I have a stack built that includes only a `Table` ...
# help
c
I have a stack built that includes only a
Table
construct for DynamoDB. When I build and deploy the stack, the resources get created as expected in my AWS account, but SST reports that the deploy failed because my stack ‘has no resources in it’. Any idea what could be causing this?
I figured out the issue and it appears to be a bug with the latest version of SST that introduces the
--profile
support. If using the
--profile
flag in the SST command, it appears the read to retrieve the stack information does not work, even though it can create the stack just fine. If I instead export my profile and run the command without the flag, everything works as it should.
f
Oh wow glad u figured it out. Taking a look into it rn.
b
Good spot!
f
@Cody Dunlap this should be fixed in v0.69.5. Can you give it a try and let me know if it works for you?
c
Sorry it took so long for the feedback but this seems to have addressed the issue for all of the constructs that I am using. Thank you!