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
When there are no changes in the configuration concerning values for 'ttl' and 'max_ttl', Terraform plan/apply should not mark the exact configuration as 'to be changed'
Actual Behavior
It seems that although the provider requires human readable format to be passed, in the state it is stored in seconds, and triggering a change for the plan/apply. With other resources where we control 'ttl' and 'max_ttl' this is behaviour is not present.
Relevant Error/Panic Output Snippet
# module.order.module.ssh["81d98dfa-aa76-42d6-8ee0-0fc3ab9e0548_ssh-poc"].vault_ssh_secret_backend_role.client_signer will be updated in-place~ resource "vault_ssh_secret_backend_role""client_signer" {
+ default_user = (known after apply)
id = "ssh/roles/ssh-poc-client_signer"~ max_ttl = "3600" ->"60m"
name = "ssh-poc-client_signer"~ ttl = "1800" ->"30m"# (18 unchanged attributes hidden)
}
Terraform Core Version
1.9.5
Terraform Vault Provider Version
4.2.0
Vault Server Version
1.7.5
Affected Resource(s)
vault_ssh_secret_backend_role
Expected Behavior
When there are no changes in the configuration concerning values for 'ttl' and 'max_ttl', Terraform plan/apply should not mark the exact configuration as 'to be changed'
Actual Behavior
It seems that although the provider requires human readable format to be passed, in the state it is stored in seconds, and triggering a change for the plan/apply. With other resources where we control 'ttl' and 'max_ttl' this is behaviour is not present.
Relevant Error/Panic Output Snippet
Terraform Configuration Files
Resource definition in the module
Locals configuration in the repository
orders/ssh.yaml for values
Steps to Reproduce
Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: