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

Skip to content

destination_config for event_source_mapping not working #151

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.

Sign up for GitHub

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

Jump to bottom
Closed
byrneo opened this issue May 18, 2021 · 6 comments
Closed

destination_config for event_source_mapping not working #151

byrneo opened this issue May 18, 2021 · 6 comments

Comments

@byrneo
Copy link
Contributor

byrneo commented May 18, 2021

Description

Setting a destination_config block within event_source_mapping doesn't appear to have any effect.

dynamodb_items_history = {
            event_source_arn  = xxxxx
            starting_position = "LATEST"
            destination_config = {
                on_failure = {
                    destination_arn = xxxxx
                }
            }
        }

Looking at the source in main.tf it appears to be commented out. Will this be enabled in an upcoming release?

⚠️ Note

Before you submit an issue, please perform the following first:

  1. Remove the local .terraform directory (! ONLY if state is stored remotely, which hopefully you are following that best practice!): rm -rf .terraform/
  2. Re-initialize the project root to pull down modules: terraform init
  3. Re-attempt your terraform plan or apply and check if the issue still persists

Versions

  • Terraform:
  • Provider(s):
  • Module:

Reproduction

Steps to reproduce the behavior:

Code Snippet to Reproduce

Expected behavior

Actual behavior

Terminal Output Screenshot(s)

Additional context
@antonbabenko
Copy link
Member

Good catch. Please open a PR if you can, and update examples/event-source-mapping.

@svenlito do you remember if there were any issues with this in provider or any other reasons back in February?

@svenlito
Copy link
Contributor

svenlito commented May 18, 2021 •
edited
Loading

@svenlito do you remember if there were any issues with this in provider or any other reasons back in February?

@antonbabenko I remember you've had issues with it not being updated/deleted when the plan changed. This was a few provider versions back. Might be worth reevaluating.

@antonbabenko
Copy link
Member

@byrneo Please raise a PR if you can.

@byrneo
Copy link
Contributor Author

byrneo commented May 20, 2021

@antonbabenko @svenlito I created #152

The pre-commit hook re-formatted some unrelated code but i added those to the PR

@antonbabenko
Copy link
Member

Thanks, @byrneo !

v2.1.0 has been just released.

@github-actions
Copy link

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 10, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@antonbabenko @byrneo @svenlito