Closed eschrock closed 1 year ago
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
This issue was automatically closed because of stale in 10 days
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
The authorizer example has the following code:
This makes it seem like you can just reference the authorizer key and don't need to specify the authorization type within the integration. However, the module code doesn't reference the authorizer_key.
The result is that if you use the
authorizer_key
the authorization type is alwaysNONE
. Either it should pull the type from key like it does with the ID, or the example should be updated to explicitly setauthorization_type
in addition toauthorizer_key
. As a casual user, the first seems more intuitive to me but I don't know if that was an explicit decision or not. The workaround is to always set theauthorization_type
even when usingauthorizer_key
Versions
v2.2.0
Terraform v1.2.9
Provider version(s):
provider registry.terraform.io/hashicorp/archive v2.2.0
provider registry.terraform.io/hashicorp/aws v4.32.0
provider registry.terraform.io/hashicorp/external v2.2.2
provider registry.terraform.io/hashicorp/local v2.2.3
provider registry.terraform.io/hashicorp/null v3.1.1
provider registry.terraform.io/hashicorp/random v3.4.3
provider registry.terraform.io/hashicorp/tls v4.0.3
Reproduction Code [Required]
Steps to reproduce the behavior:
Follow the example to create an authorizer and reference it by
authorizer_key
.Expected behavior
The authorization type will match that of the declared authorizer (e.g.
JWT
)Actual behavior
The authorization type is always set to
NONE