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: Coalesce local resolve_conflicts_on_create_default value to a boolean since default is null #3221

Merged

Conversation

bryantbiggs
Copy link
Member

Description

  • Coalesce local resolve_conflicts_on_create_default value to a boolean since default is null

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
    • reproduced in a local locals {} block
  • I have executed pre-commit run -a on my pull request

bryantbiggs referenced this pull request Nov 26, 2024
…ddons (due to retries) (#3218)

* feat: Improve addon dependency chain and decrease time to provision addons (due to retries)

* fix: Run pre-commit to clean up docs
@bryantbiggs bryantbiggs merged commit 35388bb into terraform-aws-modules:master Nov 26, 2024
18 checks passed
@bryantbiggs bryantbiggs deleted the fix/addon-conflict branch November 26, 2024 20:35
antonbabenko pushed a commit that referenced this pull request Nov 26, 2024
## [20.30.1](v20.30.0...v20.30.1) (2024-11-26)

### Bug Fixes

* Coalesce local `resolve_conflicts_on_create_default` value to a boolean since default is `null` ([#3221](#3221)) ([35388bb](35388bb))
@antonbabenko
Copy link
Member

This PR is included in version 20.30.1 🎉

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 Dec 27, 2024
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.

Latest release (20.30.0) introduced a null error condition bug
2 participants