Skip to content
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

Add alias information to serverless info command #2

Closed
HyperBrain opened this issue Mar 2, 2017 · 4 comments
Closed

Add alias information to serverless info command #2

HyperBrain opened this issue Mar 2, 2017 · 4 comments
Assignees
Labels
Milestone

Comments

@HyperBrain
Copy link
Member

serverless alias should show a list of deployed aliases.

This is helpful if you want to get an overview or want to remove aliases that are not needed anymore and consume resources for nothing.

@HyperBrain HyperBrain self-assigned this Mar 2, 2017
@HyperBrain HyperBrain added this to the beta1 milestone Mar 2, 2017
@arabold
Copy link

arabold commented Mar 2, 2017

I suggest to make this part of the built-in serverless info command instead.

@HyperBrain
Copy link
Member Author

HyperBrain commented Mar 2, 2017

I can try to do that (if hooks are available in that area)... hooks work. Expect it to be there soon.

@HyperBrain HyperBrain changed the title Add alias command Add alias information to serverless info command Mar 2, 2017
HyperBrain pushed a commit that referenced this issue Mar 3, 2017
There is an issue with the APIGateway::getDeployment() REST API function. According to the documentation it should return the API layout, but it does not.
@HyperBrain
Copy link
Member Author

Currently the APIG deployed stage details cannot be shown. It seems that there is a bug in AWS::APIGateway::getDeployment() that prevents the return of the apiSummary object, which we need here. As soon as they've fixed the issue the functionality can be enabled again.

@HyperBrain
Copy link
Member Author

Due to the AWS issue mentioned in the comment above I created a separate task for the APIG information.
See Issue #3 So this one can be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants