Azure / Azure/bicep-types-az

Microsoft.RecoveryServices vaults/backupPolicies scheduleRuntimes string[] format

Open
#2,445 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Needs: Triage :mag:
Dominant language
TypeScript
Stars
108
Forks
44
Avg merge
18h 53m
Merged PRs (30d)
29

Description

The syntax of the string[] scheduleRunTimes for V2 policies has to be documented in some way. It should be ISO 8601 extended format with milliseconds instead of ISO 8601 extended format without milliseconds. The only place this is visible is by reverse engineering an ARM-template.

Format: ISO 8601 extended format with milliseconds.
Structure: 'yyyy-MM-ddTHH:mm:ss.SSSZ'

Format: ISO 8601 extended format without milliseconds.
Structure: 'yyyy-MM-ddTHH:mm:ssZ'

The documentation at https://learn.microsoft.com/en-us/azure/templates/microsoft.recoveryservices/vaults/backuppolicies?pivots=deployment-language-bicep#dailyschedule does not suggest anything other than strings.

The linter does not show any error.

The error you get upon the deployment is:
Status 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 (Code:BMSUserErrorInvalidPolicyInput)

Quickstart-template is without milliseconds
https://github.com/Azure/azure-quickstart-templates/blob/master/quickstarts/microsoft.recoveryservices/recovery-services-daily-backup-policy-create/azuredeploy.parameters.json

At runtime the format is always: ISO 8601 extended format without milliseconds.

I'll provide some code for recreational purpose tomorrow.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the DailySchedule documentation page and compare its scheduleRunTimes description with quickstarts/microsoft.recoveryservices/recovery-services-daily-backup-policy-create/azuredeploy.parameters.json. Resolve the conflicting milliseconds formats from the deployment behavior, then document the authoritative format so the schema guidance and quickstart agree.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
cloud, documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.