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

[AVM Question/Feedback]: template does not respect TFNFR1 #102

Open
1 task done
zioproto opened this issue Apr 5, 2024 · 3 comments
Open
1 task done

[AVM Question/Feedback]: template does not respect TFNFR1 #102

zioproto opened this issue Apr 5, 2024 · 3 comments

Comments

@zioproto
Copy link
Contributor

zioproto commented Apr 5, 2024

Check for previous/existing GitHub issues

  • I have checked for previous/existing GitHub issues

Description

I was checking TFNFR1

https://azure.github.io/Azure-Verified-Modules/specs/terraform/#id-tfnfr1---category-documentation---descriptions

And I believe the customer_managed_key variable in the template does not respect TFNFR1

# required AVM interfaces
# remove only if not supported by the resource
# tflint-ignore: terraform_unused_declarations
variable "customer_managed_key" {
type = object({
key_vault_resource_id = optional(string)
key_name = optional(string)
key_version = optional(string, null)
user_assigned_identity_resource_id = optional(string, null)
})
default = {}
description = "Customer managed keys that should be associated with the resource."
}

@zioproto
Copy link
Contributor Author

zioproto commented Apr 5, 2024

Also lock is missing the example in the description:

variable "lock" {
type = object({
name = optional(string, null)
kind = optional(string, "None")
})
default = {}
description = "The lock level to apply. Default is `None`. Possible values are `None`, `CanNotDelete`, and `ReadOnly`."
nullable = false
validation {
condition = contains(["CanNotDelete", "ReadOnly", "None"], var.lock.kind)
error_message = "The lock level must be one of: 'None', 'CanNotDelete', or 'ReadOnly'."
}
}

@prjelesi
Copy link

@matt-FFFFFF

@matt-FFFFFF
Copy link
Member

I think the NFR needs changing to MAY

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Needs: Triage
Development

No branches or pull requests

3 participants