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: Update dynamic lookup logic to support lazy evaluation #19

Merged
merged 1 commit into from
Jun 23, 2022

Conversation

bryantbiggs
Copy link
Member

Description

  • Update dynamic lookup logic to support lazy evaluation and using resource attributes within the map definitions
  • Update to use data source for DNS suffix on assume role entities

Motivation and Context

Breaking Changes

  • No

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

@bryantbiggs bryantbiggs requested a review from antonbabenko June 23, 2022 17:26
@@ -176,7 +177,8 @@ resource "aws_dms_endpoint" "this" {

# https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Target.Elasticsearch.html
dynamic "elasticsearch_settings" {
for_each = try([each.value.elasticsearch_settings], [])
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

try() was great, but I guess theres still a place for lookup() too 😬

@bryantbiggs bryantbiggs merged commit 8fb0daa into master Jun 23, 2022
@bryantbiggs bryantbiggs deleted the fix/lazy-resolution branch June 23, 2022 17:41
antonbabenko pushed a commit that referenced this pull request Jun 23, 2022
### [1.5.2](v1.5.1...v1.5.2) (2022-06-23)

### Bug Fixes

* Update dynamic lookup logic to support lazy evaluation ([#19](#19)) ([8fb0daa](8fb0daa))
@antonbabenko
Copy link
Member

This PR is included in version 1.5.2 🎉

@github-actions
Copy link

github-actions bot commented Nov 8, 2022

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 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
2 participants