terraform-aws-eks-blueprints-addons icon indicating copy to clipboard operation
terraform-aws-eks-blueprints-addons copied to clipboard

Question about tag: v1.12.0

Open carlosj934 opened this issue 1 year ago • 4 comments

Discussed in https://github.com/aws-ia/terraform-aws-eks-blueprints-addons/discussions/385

Originally posted by carlosj934 April 5, 2024 Hello, I was curious if anyone could point out which commit hash is associated to version = "~> 1.12". It looks like when trying to use this version, tag: v1.16.0 aligns closer to the version rather than tag: v1.12.0. Thank you! @askulkarni2

carlosj934 avatar Apr 08 '24 16:04 carlosj934

@bryantbiggs

carlosj934 avatar Apr 08 '24 16:04 carlosj934

Hi - I don't quite follow, what exactly are you trying to do?

For ref, here is a diff between 1.12 and 1.16 https://github.com/aws-ia/terraform-aws-eks-blueprints-addons/compare/v1.12.0...v1.16.0

bryantbiggs avatar Apr 08 '24 16:04 bryantbiggs

Hi - I don't quite follow, what exactly are you trying to do?

For ref, here is a diff between 1.12 and 1.16 v1.12.0...v1.16.0

Hello, I have a local version of this repo that I'm sourcing for my personal project. When I source it directly from the terraform registry I would point it at version ~>1.12 but when trying change my source to be pointing at the locally hosted version of this module it seems like tag v1.16.0 keeps my environment the same but tag v1.12.0 is rolling back the versions of alb controller helm release and making a change the IAM policy of the alb controller. So I was just curious if there was a difference between the version numbers on the terraform registry compared to the tag numbers on github. Thank you! @bryantbiggs

carlosj934 avatar Apr 08 '24 16:04 carlosj934

This issue has been automatically marked as stale because it has been open 30 days with no activity. Remove stale label or comment or this issue will be closed in 10 days

github-actions[bot] avatar May 09 '24 00:05 github-actions[bot]