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

fix: Qualifiers in event invoke config #368

Merged
merged 1 commit into from
Oct 27, 2022

Conversation

sindrig
Copy link
Contributor

@sindrig sindrig commented Oct 27, 2022

Description

create_current_version_async_event_config and create_unqualified_alias_async_event_config were not working due to zipmap returning a map with qualifier as key and null as value if variables were set to false

Motivation and Context

there's currently no way to opt out of either current_version or unqualified_version for async event config

How Has This Been Tested?

  • I have updated at least one of the examples/* to demonstrate and validate my change(s)
  • I have tested and validated these changes using one or more of the provided examples/* projects
  • I have executed pre-commit run -a on my pull request

I deployed the examples/alias example and modified the variables before my change, resulting in no change in terraform state. Then I applied my change and ran apply, and terraform wanted to remove the resources, as it should.

create_current_version_async_event_config and
create_unqualified_alias_async_event_config were not working due
to zipmap returning a map with qualifier as key and null as value
if variables were set to false
@sindrig sindrig changed the title Fix qualifiers in event invoke config fix: Qualifiers in event invoke config Oct 27, 2022
@antonbabenko antonbabenko merged commit 93e1dc3 into terraform-aws-modules:master Oct 27, 2022
antonbabenko pushed a commit that referenced this pull request Oct 27, 2022
### [4.2.1](v4.2.0...v4.2.1) (2022-10-27)

### Bug Fixes

* Qualifiers in event invoke config ([#368](#368)) ([93e1dc3](93e1dc3))
@antonbabenko
Copy link
Member

This PR is included in version 4.2.1 🎉

@github-actions
Copy link

I'm going to lock this pull request 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 related to this change, 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 27, 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 this pull request may close these issues.

2 participants