You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By the default, when we deploy the first version without alias option, the plugin creates a master CF stack name with suffix is (dev) i.e. sls-test-project-dev, also APIG is creating with dev prefix i.e. dev-sls-test-project. Is that possible to not adding suffix/prefix to APIG and Master CF stacks?
In fact, we only want to just create a master CF for the serverless with the name that we named in the serverless.yml (e.g. sls-test-project), also APIG name should the same. Adding prefix to APIG will make us confused that we will have more APIGs to be created for the same project which will never happen when using this plugin.
The text was updated successfully, but these errors were encountered:
I created PR #156 that would allow setting the master alias upon first deployment using sls deploy --masterAlias <masterAliasName>. Could you please check if this satisfies your requirements? Thanks
By the default, when we deploy the first version without alias option, the plugin creates a master CF stack name with suffix is (dev) i.e. sls-test-project-dev, also APIG is creating with dev prefix i.e. dev-sls-test-project. Is that possible to not adding suffix/prefix to APIG and Master CF stacks?
In fact, we only want to just create a master CF for the serverless with the name that we named in the serverless.yml (e.g. sls-test-project), also APIG name should the same. Adding prefix to APIG will make us confused that we will have more APIGs to be created for the same project which will never happen when using this plugin.
The text was updated successfully, but these errors were encountered: