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

Show APIG information on serverless info #3

Open
HyperBrain opened this issue Mar 3, 2017 · 3 comments
Open

Show APIG information on serverless info #3

HyperBrain opened this issue Mar 3, 2017 · 3 comments
Assignees

Comments

@HyperBrain
Copy link
Member

Additionally to function information, the plugin should display APIG information of the deployed APIG stages when invoked by serverless info.

@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 HyperBrain added this to the beta milestone Mar 3, 2017
@HyperBrain
Copy link
Member Author

AWS confirmed that there is a bug in the ApiGateway REST API. So I keep this as "blocked" until I receive further information.

@HyperBrain HyperBrain self-assigned this Mar 7, 2017
@HyperBrain
Copy link
Member Author

Got an answer. There is a workaround to get the API summary information on a deployed APIG stage.

Meanwhile you can consider trying to manually retrieve the apisummary by using the 'embed' query parameter. If you pass in "embed=apisummary" in the request, you will get the apisummary part as well.

The parameter value must be a single-valued list containing only the "apisummary" string. For example, GET /restapis/{restapi_id}/deployments/{deployment_id}?embed=apisummary. Please see [1] to know more about this.

[1] : http://docs.aws.amazon.com/apigateway/api-reference/link-relation/deployment-by-id/

Nevertheless this would mean that there has to be a HTTP client in the implementation which would just be temporary. Maybe the client in the AWS SDK can be used directly here, to not add additional dependencies.

@HyperBrain HyperBrain removed this from the beta milestone May 24, 2017
mattsemar pushed a commit to mattsemar/serverless-aws-alias that referenced this issue Apr 20, 2022
Migrate to Artifactory

* migrate to artifactory

* update docker image for CCI

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

No branches or pull requests

1 participant