-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
URL output format #70
Comments
As the alias is technically an API Gateway Stage, the way to achieve your layout is, to add a custom domain mapping to your APIG API. Select "Custom domain names" in the AWS APIG console. Then add an URL mapping (e.g. custom domain Then you can access the different aliases as: Remember to add a DNS alias entry for the CloudFront distribution name generated by the mapping to This also has the advantage, that you can map multiple APIG APIS (serverless services) to one domain with the first path element being different for each service (like /api, /users, etc.) |
ok, sounds like a plan. Do you think its a good idea to use it for versioning? |
You can try. We use it currently at work for developer branch deployments, but using it for versioning also sounds good. Please give it a try and let me know if it works for that use case. Maybe I cann add this use case to the README later. |
Ok. I also need something like this, I'd like to hear some opinions :) Thanks for your time |
Hi there,
I intend to use this plugin for versioning purposes:
Master
serverless --stage dev
Versions
serverless --stage dev --alias v1
serverless --stage dev --alias v2
Endpoints
https://{{domain}}.execute-api.eu-west-1.amazonaws.com/{{alias}}/resource
My question is, can I customize the alias format so it becomes with the plugin?
https://{{domain}}.execute-api.eu-west-1.amazonaws.com/api/{{alias}}/resource
Note the /api/ before the {{alias}}
@thanks!
The text was updated successfully, but these errors were encountered: