Skip to content

fix: spec for list keys api functions webapp#33565

Open
munishsuri wants to merge 7 commits intoAzure:mainfrom
munishsuri:bug/webappscl/listfk
Open

fix: spec for list keys api functions webapp#33565
munishsuri wants to merge 7 commits intoAzure:mainfrom
munishsuri:bug/webappscl/listfk

Conversation

@munishsuri
Copy link

@munishsuri munishsuri commented Mar 28, 2025

Choose a PR Template

Switch to "Preview" on this description then select one of the choices below.

Response from Spec of List Keys currently points to String dictionary , which is not correct, it should be function keys , as depicted in the screenshot.

  1. Changing the Spec to Correct Info
  2. Creating a definition for function key

Screenshot 2025-03-27 at 3 42 06 PM

Click here to open a PR for a Data Plane API.

Click here to open a PR for a Control Plane (ARM) API.

Click here to open a PR for only SDK configuration.

@munishsuri munishsuri requested a review from naveedaz as a code owner March 28, 2025 13:25
@openapi-pipeline-app
Copy link

openapi-pipeline-app bot commented Mar 28, 2025

Next Steps to Merge

Next steps that must be taken to merge this PR:
  • ❌ This PR targets either the main branch of the public specs repo or the RPSaaSMaster branch of the private specs repo. These branches are not intended for iterative development. Therefore, you must acknowledge you understand that after this PR is merged, the APIs are considered shipped to Azure customers. Any further attempts at in-place modifications to the APIs will be subject to Azure's versioning and breaking change policies. Additionally, for control plane APIs, you must acknowledge that you are following all the best practices documented by ARM at aka.ms/armapibestpractices. If you do intend to release the APIs to your customers by merging this PR, add the PublishToCustomers label to your PR in acknowledgement of the above. Otherwise, retarget this PR onto a feature branch, i.e. with prefix release- (see aka.ms/azsdk/api-versions#release--branches).
  • ❌ This PR is in purview of the ARM review (label: ARMReview). This PR must get ARMSignedOff label from an ARM reviewer.
    This PR is not ready for ARM review (label: NotReadyForARMReview). This PR will not be reviewed by ARM until relevant problems are fixed. Consult the rest of this Next Steps to Merge comment for details.
    Once the blocking problems are addressed, add to the PR a comment with contents /azp run. Automation will re-evaluate this PR and if everything looks good, it will add WaitForARMFeedback label which will put this PR on the ARM review queue.
    For details of the ARM review, see aka.ms/azsdk/pr-arm-review
  • ❌ This PR is NotReadyForARMReview because it has the BreakingChangeReviewRequired label.
  • ❌ This PR has at least one breaking change (label: BreakingChangeReviewRequired).
    To unblock this PR, follow the process at aka.ms/brch.
  • ❌ The required check named Swagger BreakingChange has failed. To unblock this PR, follow the process at aka.ms/brch.

@openapi-pipeline-app
Copy link

openapi-pipeline-app bot commented Mar 28, 2025

PR validation pipeline restarted successfully. If there is ApiView generated, it will be updated in this comment.

@github-actions
Copy link

github-actions bot commented Apr 8, 2025

API Change Check

APIView identified API level changes in this PR and created the following API reviews

Language API Review for Package
Java com.azure.resourcemanager:azure-resourcemanager-appservice-generated
JavaScript @azure/arm-appservice

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ARMReview BreakingChangeReviewRequired <valid label in PR review process>add this label when breaking change review is required customer-reported Issues that are reported by GitHub users external to the Azure organization. NotReadyForARMReview resource-manager Web Apps

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants