Open ralimardanov opened 2 months ago
Voting for Prioritization
Volunteering to Work on This Issue
https://github.com/hashicorp/terraform-provider-aws/issues/31364 I see in this issue that there is another provider resource that can be used - awscc_osis_pipeline, but it's not recommended to use. VPC attachment is implemented in that resource - https://github.com/hashicorp/terraform-provider-awscc/blob/main/internal/aws/osis/pipeline_resource_gen.go#L601-L623.
Hey @ralimardanov 👋 Thanks for taking the time to raise this! It looks like this ultimately comes down to the need for an additional argument for vpc_attachment_options
. We consider additions to existing resources to be an enhancement, rather than a bug. With that in mind, I'm going to update a few things about this issue. There's no further action needed from you at this point, I just like to let people know before making these kinds of modifications.
Terraform Core Version
1.3.1
AWS Provider Version
5.63.0
Affected Resource(s)
aws_osis_pipeline
Expected Behavior
It should create osis pipeline with vpc endpoint.
Actual Behavior
During terraform apply I get an error:
Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
Steps to Reproduce
To reproduce you should have DocumentDB cluster and Opensearch domain. Pipeline will connect to DocumentDB collection, get documents, store in s3 bucket and then process to Opensearch domain. The issue is when you try to use VPC endpoints instead of public access. Terraform resource is missing VPC attachment and VPC CIDR options. I assume it wasn't implemented yet. Do you have any workaround for that or any ETA when it will be implemented? Thanks.
Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
No