-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
[azurerm_redis_cache] Backup settings don't seem to be enabled #2634
Comments
for me the 'rdb_backup_max_snapshot_count' doesn't work, fails if I set it different from 1.
|
Any update on this? Should we even use this attribute? |
Thanks for opening this issue. After tested with below tfconfig and latest azurerm, seems I cannot repro this issue anymore. Could you have a try below tfconfig to check whether this issue still exists?
|
👋 Since we've not heard back here I'm going to close this issue for the moment - but please let us know if the solution proposed above doesn't work and we'll take another look. Thanks! |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks! |
Community Note
Terraform (and AzureRM Provider) Version
Affected Resource(s)
azurerm_redis_cache
Terraform Configuration Files
Calling module
Definition
Debug Output
If you need this, contact me as it contains sensitive items not wanting exposed publically
Expected Behavior
Based on what I understand, when I go to Azure portal, Redis data persistance should be enabled. I see the the values being set when I view the output from the plan generated
Actual Behavior
When I go to the Azure portal for my redis cache, the redis data persistance is turned off.
Steps to Reproduce
Simply perform the three-step terraform process of
References
The text was updated successfully, but these errors were encountered: