You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe there is a regression in authentication_mode introduced in 20.11.1. Changing the value of authentication_mode from API_AND_CONFIG_MAP -> API results in "No changes. Your infrastructure matches the configuration." Pinning module version 20.11.0 results in the expected changes to authentication_mode being recognized by Terraform.
My hunch is that this ignore change is actually ignoring the entire access_config block and not just bootstrap_cluster_creator_admin_permissions
✋ I have searched the open/closed issues and my issue is not listed.
⚠️ Note
Before you submit an issue, please perform the following first:
Remove the local .terraform directory (! ONLY if state is stored remotely, which hopefully you are following that best practice!): rm -rf .terraform/
Re-initialize the project root to pull down modules: terraform init
Re-attempt your terraform plan or apply and check if the issue still persists
module "data" {
source = "terraform-aws-modules/eks/aws"
version = "20.12.0"
authentication_mode = "API_AND_CONFIG_MAP" # Toggling this value to "API" results in no changes to infrastructure
}
Steps to reproduce the behavior:
Not using workspace and local cache cleared many times during troubleshooting this issue.
Upgraded to latest v20 (20.12.0)
Attempted to switch authentication_mode from API_AND_CONFIG_MAP to API
terraform plan results in "No changes. Your infrastructure matches the configuration."
Pin to module version 20.11.1 and try again == same result
Pin to module versoin 20.11.0 and try again == working as expected
Expected behavior
I would expect that changing the authentication_mode to a valid value would result in the appropriate changes being present in my terraform plan
Actual behavior
Changing the authentication_mode to a valid value does not result in any changes to infrastructure when running terraform plan
Terminal Output Screenshot(s)
Additional context
The text was updated successfully, but these errors were encountered:
I'm going to lock this issue 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 similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Description
I believe there is a regression in
authentication_mode
introduced in 20.11.1. Changing the value ofauthentication_mode
fromAPI_AND_CONFIG_MAP
->API
results in "No changes. Your infrastructure matches the configuration." Pinning module version 20.11.0 results in the expected changes toauthentication_mode
being recognized by Terraform.My hunch is that this ignore change is actually ignoring the entire
access_config
block and not justbootstrap_cluster_creator_admin_permissions
Before you submit an issue, please perform the following first:
.terraform
directory (! ONLY if state is stored remotely, which hopefully you are following that best practice!):rm -rf .terraform/
terraform init
Versions
Module version [Required]: 20.12.0
Terraform version: v1.8.4
Reproduction Code [Required]
Steps to reproduce the behavior:
Not using workspace and local cache cleared many times during troubleshooting this issue.
API_AND_CONFIG_MAP
toAPI
terraform plan
results in "No changes. Your infrastructure matches the configuration."Expected behavior
I would expect that changing the
authentication_mode
to a valid value would result in the appropriate changes being present in myterraform plan
Actual behavior
Changing the
authentication_mode
to a valid value does not result in any changes to infrastructure when runningterraform plan
Terminal Output Screenshot(s)
Additional context
The text was updated successfully, but these errors were encountered: