Increase max staleness prefix for multiple regions and fix documentation

[azmelanar]

Hi,

In this PR two fixes:

• fix in documentation, because key is unknown during planning
  Error: azurerm_cosmosdb_account.cosmosdb: consistency_policy.0: invalid or unknown key: max_staleness
• increase max_staleness_prefix, because
  The maximum lag must be between 5 seconds and 1 day for accounts with a single region, and between 5 minutes and 1 day for accounts with multiple regions.

Please let me know, if there are any questions.

Thanks

[katbyte]

Hello @azmelanar,

Thank you for noticing this and submitting a fix! Aside from a minor update to the documentation LGTM. I'll get this merged for you shortly 🙂

[katbyte]

Tests pass:

[lorenyu]

Does it make sense to increate the default values, or to change the example to use a higher value for max staleness? Since the example is across multiple regions, the default of 5 seconds / 100 operations isn't allowed in Azure. People who try out the example would end up seeing this error:

[ghost]

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!