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

Deleting AWS API GW domain base path mapping with the empty base path fails #9212

Closed
rafal-gancarz-opencredo opened this issue Oct 4, 2016 · 3 comments · Fixed by #10177
Closed

Comments

@rafal-gancarz-opencredo
Copy link

Hi there,

After creating a base path mapping with an empty base path (an optional attribute) for the custom domain TF doesn't seem to be able to destroy it.

This is because the API (http://docs.aws.amazon.com/apigateway/api-reference/link-relation/basepathmapping-delete/) requires to use the special value of (none) for the path variable base_path to denote the empty base path and Terraform doesn't set the path variable correctly.

Terraform version: 0.7.4
Affected resource: aws_api_gateway_base_path_mapping
Debug output: https://gist.github.com/rafal-gancarz-opencredo/5ca8a05cf600b0947519a94f0457d566

@d2chau
Copy link

d2chau commented Oct 19, 2016

I too have verified this.

The AWS cli also requires a parameter of "(none)" passed in.
aws apigateway delete-base-path-mapping --domain-name "sub-domain.domain.com" --base-path "(none)"

If it is ran with an empty string,
aws apigateway delete-base-path-mapping --domain-name "sub-domain.domain.com" --base-path ""
The response is No JSON object could be decoded

@Ninir
Copy link
Contributor

Ninir commented Dec 4, 2016

Hi guys,
Made some work on this here. Hope it will fit :)

@ghost
Copy link

ghost commented Apr 18, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 18, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants