terraform-aws-route53
terraform-aws-route53 copied to clipboard
feat(modules/zone): Complex variable types
use descriptive variable types.
versions.tf already specifies higher than 1.3.0 so no change needed there.
This PR has been automatically marked as stale because it has been open 30 days with no activity. Remove stale label or comment or this PR will be closed in 10 days
Not stale
This PR has been automatically marked as stale because it has been open 30 days with no activity. Remove stale label or comment or this PR will be closed in 10 days
This is really nice!
Any chance of getting your input here @antonbabenko ?
This is really nice!
Any chance of getting your input here @antonbabenko ?
Yes, I plan to get back to this and many other PRs in terraform-aws-modules after AWS reinvent.
This PR has been automatically marked as stale because it has been open 30 days with no activity. Remove stale label or comment or this PR will be closed in 10 days
How was re:invent @antonbabenko ? π
How was re:invent @antonbabenko ? π
@BeyondEvil Thanks for asking, it went well - https://www.youtube.com/watch?v=fX7c2GGqTWs π
How was re:invent @antonbabenko ? π
@BeyondEvil Thanks for asking, it went well - https://www.youtube.com/watch?v=fX7c2GGqTWs π
Oh nice! I'll have a look. π
This PR has been automatically marked as stale because it has been open 30 days with no activity. Remove stale label or comment or this PR will be closed in 10 days
ping @kevcube
not stale
This PR has been automatically marked as stale because it has been open 30 days with no activity. Remove stale label or comment or this PR will be closed in 10 days
not stale
I might be able to fix the issue in a couple of weeks if @kevcube doesn't respond.
This PR has been automatically marked as stale because it has been open 30 days with no activity. Remove stale label or comment or this PR will be closed in 10 days
This PR was automatically closed because of stale in 10 days
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.
This issue has been resolved in version 6.0.0 :tada: