stage not respected

[ifavo]

I am deploying a container with different sages, both are built and pushed to the container registry and deployed on the namespace/container.

They should be different when running these two commands:

serverless deploy --stage preview
serverless deploy --stage production

But the second one replaces the first one.

How can I deploy to different stages?

[thomas-tacquet]

Hello 👋

Thanks for reporting this, can you share just the part you use stages in your configuration file to reproduct the issue ?

It seems not well supported by the ServerlessCom framework when we have a provider different than those who are mentionned in the official documentation 🤔 If confirmed we can add custom support for this argument

Meanwhile I can suggest you to use env variable (example here https://github.com/scaleway/serverless-scaleway-functions#security-and-secret-management ) to manage stages manually

[ifavo]

I have not configured a specific stage in the configuration. In other projects deployments when deployed to lambda (in combination with serverless-lift plugin), it will generate a unique name for each stage and deploy there. Not changing the configuration for each stage is why I like to use the serverless framework.

I would rather not implement a workaround and instead wait a bit, if this could be supported in the nearby future.

[ifavo]

@thomas-tacquet do you plan on supporting the stage option from serverless or will you leave it like it is?