Closed jritsema closed 5 months ago
we (typically) pull the argument description directly from upstream - this is the value that they currently have, but I have not checked if RDS has made changes that have relaxed/expanded support for this https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/rds_cluster#enable_http_endpoint
It looks like the doc comment is incorrect and there's a PR in flight in the provider to resolve. It didn't appear to work but I will test again and update here. https://github.com/hashicorp/terraform-provider-aws/pull/35691
I can verify that the doc in this project is incorrect.
Enable HTTP endpoint (data API). Only valid when engine_mode is set to serverless
Enabling HTTP endpoint (data API) does work when engine_mode is provisioned
. It cannot be changed after creation which explains what I was seeing.
Here is the open issue in the provider for this. Looks like someone closed the associated PR that would change the description to the following:
Enable HTTP endpoint (data API). Only valid when `engine_mode` is set to `serverless` or when `engine` is set to `aurora-postgresql` and `engine_mode` is set to `provisioned`.
I can submit a PR in this repo, however, I understand if you want to wait and pull from upstream.
We found a case that with engine
is set to aurora-postgresql
and engine_mode
is set to provisioned
, the terraform said the change is applied, but from AWS console , it still shows the Data API disabled.
Does anyone know what's going on here ? Is there a way to troubleshooting ?
We found a case that with
engine
is set toaurora-postgresql
andengine_mode
is set toprovisioned
, the terraform said the change is applied, but from AWS console , it still shows the Data API disabled.Does anyone know what's going on here ? Is there a way to troubleshooting ?
Might want to double check you are in a supported region, that was my issue. This is only supported in 4 regions right now:
It will fail silently if executed in a region without support
This issue has been automatically marked as stale because it has been open 30 days with no activity. Remove stale label or comment or this issue will be closed in 10 days
This issue was automatically closed because of stale in 10 days
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.
Description
For
enable_http_endpoint
, the docs say:I was able to enable this when creating a serverless v2 cluster using the AWS console, so are the docs correct here?
When I tested it in Terraform, it appears to try setting it but ultimately did not work.
If your request is for a new feature, please use the
Feature request
template.Versions
Module version [Required]:
9.2.1
Terraform version:
Provider version(s):
provider registry.terraform.io/hashicorp/aws v5.41.0
Reproduction Code [Required]
Steps to reproduce the behavior:
Expected behavior
Actual behavior
Terminal Output Screenshot(s)
Additional context