is it possible to bypass sst's custom stack name string manipulation and use a non-prepended string to guide which stack to deploy in a multi-stack process?

can you expand on this a bit more

Sure @thdxr, so currently if you do

sst deploy stackname

it will actually deploy something more along the lines of

sst deploy stage-name-stackname

where

stage

and

name

are coming from

sst.json

Now, this is fine in most cases, but i'm having an emergent issue from a misnaming in our

sst.json

so now the deploys are pre-pending the stage and name and making it difficult to deploy a singular stack. So, my question is, can i override the behavior of doing

sst deploy stage-name-stackname

to instead only take the stackname with no string manipulation whatsover

ah I'm not sure this is currently possible

@David Garcia which version of SST r u using?

0.46.1

In recent versions:

new ApiStack(app, "api", {stackName: "my-custom-dev-api-stack"});

Running

sst deploy api

should work

Heard that, I appreciate the information. I'll get back to you after I'm able to apply those changes. Appreciate it