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

doc: Add note about instant_restore_retention_days #24539

Merged
merged 1 commit into from
Jan 18, 2024

Conversation

jaredbrogan
Copy link
Contributor

@jaredbrogan jaredbrogan commented Jan 17, 2024

This is required per the note presented when attempting to create a weekly backup policy in the portal.
See below:
image

Otherwise, this ever-present vague error will be presented (taken from activity log):

"statusMessage": "{\"error\":{\"code\":\"BMSUserErrorInvalidPolicyInput\",\"message\":\"Input for create or update policy is not in proper format. Please check format of parameters like schedule time, schedule days, retention time and retention days \"}}",

This applies to both V1 and V2 policies.

Copy link
Collaborator

@katbyte katbyte left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this @jaredbrogan - LGTM 📄

@katbyte katbyte merged commit 657fbf4 into hashicorp:main Jan 18, 2024
5 checks passed
@github-actions github-actions bot added this to the v3.88.0 milestone Jan 18, 2024
Copy link

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 30, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants