Qi Ni
Qi Ni
> The function is designed for delete operations and is not being used anymore.
Can we make those checks in the check-in pipeline? This will save time for both of us.
> > > ``` > > > } > > > ``` > > > > > > Please review all the newly added properies in this PR and see...
> > ``` > > "operationId": "LoadBalancers_Rebalance", > > ``` > > https://github.com/Azure/azure-openapi-validator/blob/main/docs/post-operation-id-contains-url-verb.md > > Refers to: specification/containerservice/resource-manager/Microsoft.ContainerService/aks/preview/2024-03-02-preview/managedClusters.json:3836 in [19d06fc](https://github.com/Azure/azure-rest-api-specs/commit/19d06fcc530ac8b83e6452a26db4aa2e7a0cbbee). [](commit_id = [19d06fc](https://github.com/Azure/azure-rest-api-specs/commit/19d06fcc530ac8b83e6452a26db4aa2e7a0cbbee), deletion_comment = False) Can you suggest a...
For a property with only two possible values, a boolean data type is the most suitable choice. Changing it to a string enum would introduce unnecessary complexity.
We can skip checking pip when the service.status.loadbalancer.ingress is empty.
@Jasstkn can you open the issue in capz or capi? This is not a cloud provider issue.
Can we unit test this?
/lgtm /approve
/cherrypick release-1.29