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

[BUG] Recovery Services Site Recovery Replication Protected Item - Unable to manage ChurnOption via REST API #32027

Open
wyattfry opened this issue Jan 7, 2025 · 2 comments
Assignees
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. customer-reported Issues that are reported by GitHub users external to the Azure organization. Mgmt This issue is related to a management-plane library. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that

Comments

@wyattfry
Copy link

wyattfry commented Jan 7, 2025

API Spec link

https://github.com/Azure/azure-rest-api-specs/blob/main/specification/recoveryservicessiterecovery/resource-manager/Microsoft.RecoveryServices/stable/2024-10-01/service.json

API Spec version

2024-10-01

Describe the bug

The documentation for Replication Protected Items indicates that the ChurnOption should be accessible via the REST interface, however I was unable to read or set the ChurnOption in practice. When reading an "Item", the property should be under "ProviderSpecificDetails", but it is missing. It is accessible however when using version API 2023-04-01.

Expected behavior

I would expect the API to behave the way the documentation indicates it should: i.e. that there be a way to both read and set the ChurnOption.

Actual behavior

I was unable to read or set the ChurnOption via the API.

Reproduction Steps

  1. Create a Replication Protected Item via Azure Portal with High Churn
  2. Retrieve the Item via the API
  3. Note the missing ChurnOption property

Environment

N/A

@wyattfry wyattfry added the bug This issue requires a change to an existing behavior in the product in order to be resolved. label Jan 7, 2025
@microsoft-github-policy-service microsoft-github-policy-service bot added question The issue doesn't require a change to the product in order to be resolved. Most issues start as that customer-reported Issues that are reported by GitHub users external to the Azure organization. labels Jan 7, 2025
@v-jiaodi v-jiaodi added the Mgmt This issue is related to a management-plane library. label Jan 10, 2025
@v-jiaodi
Copy link
Member

@singhabh27 Please help take a look, thanks.

@wyattfry
Copy link
Author

Confirming that I'm still interested in finding an answer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. customer-reported Issues that are reported by GitHub users external to the Azure organization. Mgmt This issue is related to a management-plane library. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Projects
None yet
Development

No branches or pull requests

3 participants