Azure Recovery Services Vault InvalidRestApiParameter

Open

#702 opened on Nov 10, 2022 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 4/5
Estimated time: 3-5 days
Newbie friendliness: 35/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Stale
Tech stack: azure, powershell
Domain: cloud, devops

Research direction

Start by reproducing the issue with an Azure Recovery Services Vault, then compare the JSON-template produced by the AzOps Pull with the payload used by Push and its -WhatIf result. Done means the pulled template can be pushed without the InvalidRestApiParameter error; the payload names no source files or tests to inspect.

Written by the indexing model from the issue text.

Description

resource-provider triage

Describe the bug

When deploying the Microsoft.RecoveryServices/vaults resourceType gives the error "InvalidRestApiParameter - properties parameter is invalid. Please provide a valid properties".

Steps to reproduce

Create an Azure Recovery Services Vault
Do a Pull in AzOps
The Push will trigger and the error appears

I even reproduced it by doing the -WhatIf with the JSON-template coming from the AzOps Pull.

Screenshots

Dominant language: PowerShell
Stars: 420
Forks: 174
Avg merge: 16d 18h
Merged PRs (30d): 1

Contributor guide

No contributing guide indexed for this repository

First steps

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

Similar issues

[BUG] GkeTpuCluster queries metadata.google.internal for MEGASCALE_SLICE_ID even when TPU_SKIP_MDS_QUERY is set Open

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

jax-ml/jax#40854 · Opened Sep 22, 2026
fix(mcp): `permanently_delete_cloud_{source,destination,connection}` lack `workspace_id` param, unusable without a default workspace Open

bug

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

airbytehq/PyAirbyte#1201 · Opened Sep 21, 2026
[BUG] Route53Resolver: CreateResolverEndpoint requires IpAddressRequests, but the AWS member is IpAddresses, so no SDK client can call it Open

Difficulty 2/5 1-3 hours Newbie friendliness 84/100

floci-io/floci#4108 · Opened Sep 21, 2026
wm_gcp_parse_output underflows its heap buffer by one byte Open

level/task module/gcp type/bug

Difficulty 2/5 1-3 hours Newbie friendliness 85/100

wazuh/wazuh#39525 · Opened Sep 21, 2026
[Bug]: aws_lb_listener silently ignores tcp_idle_timeout_seconds on TCP_UDP listeners Open

bug needs-triage service/elbv2

Difficulty 2/5 1-3 hours Newbie friendliness 82/100

hashicorp/terraform-provider-aws#50100 · 1 comment · Opened Sep 21, 2026

More Cloud issues