Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Support self_managed_kafka event source mapping #277

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

Closed
kty1965 opened this issue Mar 8, 2022 · 2 comments · Fixed by #278
Closed

Support self_managed_kafka event source mapping #277

kty1965 opened this issue Mar 8, 2022 · 2 comments · Fixed by #278

Comments

@kty1965
Copy link
Contributor

kty1965 commented Mar 8, 2022

Is your request related to a new offering from AWS?

available on terraform AWS provider self-managed-apache-kafka
.

Is your request related to a problem? Please describe.

Currently, we can't connect self managed kafka.
We need to add self_managed_event_source nested block in your module.

I submit this requested at #200

Describe the solution you'd like.

If self_managed_event_source value is set, we don't need to set event_source_arn.
Only add self_managed_event_source code block.

Describe alternatives you've considered.

code main.tf on aws_lambda_event_source_mapping.this

-   event_source_arn = each.value.event_source_arn 
+   event_source_arn = lookup(each.value, "event_source_arn", null)
...

+  dynamic "self_managed_event_source" {
+    for_each = lookup(each.value, "self_managed_event_source", [])
+    content {
+      endpoints = self_managed_event_source.value["endpoints"]
+    }
+  }

Additional context

@antonbabenko
Copy link
Member

This issue has been resolved in version 3.1.0 🎉

@github-actions
Copy link

github-actions bot commented Nov 8, 2022

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 8, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants