- 
                Notifications
    You must be signed in to change notification settings 
- Fork 5.5k
Update IpAllocationDelete.json to fix the Linter Error #25201
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
          
     Merged
      
      
    
                
     Merged
            
            
          Conversation
  
    
      This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
      Learn more about bidirectional Unicode characters
    
  
  
    
    Update IpAllocationDelete.json to fix the Linter Error
| Hi, @ZhangYi19941217! Thank you for your pull request. To help get your PR merged:  Generated ApiViewcomment added to this PR. You can use ApiView to show API versions diff. | 
| Swagger Validation Report
 | 
| Swagger Generation Artifacts
 | 
| Generated ApiView
 | 
  This was referenced Aug 7, 2023 
      
| /pr RequestMerge | 
| Next Steps to Merge | 
              
                    ms-henglu
  
              
              approved these changes
              
                  
                    Aug 22, 2023 
                  
              
              
            
            
| Swagger pipeline restarted successfully, please wait for status update in this comment. | 
  This was referenced Aug 22, 2023 
      
  
    Sign up for free
    to join this conversation on GitHub.
    Already have an account?
    Sign in to comment
  
      Labels
      
    Approved-SdkBreakingChange-Python
  
    ARMReview
  
    ARMSignedOff
  <valid label in PR review process>add this label when ARM approve updates after review 
  
    FixS360
  
    ReadyForApiTest
  <valid label in PR review process>add this label when swagger and service APIs are ready for test 
  
    resource-manager
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Update IpAllocationDelete.json to fix the Linter Error ( LRO_RESPONSE_HEADER ) for Microsoft.Network: https://openapihub.azure-devex-tools.com/amekpis/linting/detail?errorId=1A6E673F-4276-41D9-B7A8-606727991FCA
ARM (Control Plane) API Specification Update Pull Request
PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.
[1] public repo review queue, private repo review queue
The PRs are processed by time opened, ascending. Your PR may show up on 2nd or later page.
If you addressed Step 1 from the diagram and your PR is not showing up in the queue, ensure the label
ARMChangesRequestedis removed from your PR. This should cause the label
WaitForARMFeedbackto be added.[2] https://aka.ms/azsdk/support/specreview-channel
[3] List of SDK breaking changes approvers in pinned Teams announcement
[4] public repo merge queue, private repo merge queue
If you need further help with anything, see
Getting helpsection below.Purpose of this PR
What's the purpose of this PR? Check all that apply. This is mandatory!
Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to Step 2, "ARM Review", for this PR.
Breaking changes review (Step 1)
you must follow the breaking changes process.
IMPORTANT This applies even if:
Such claims must be reviewed, and the process is the same.
ARM API changes review (Step 2)
ARMReviewlabel.Getting help
and https://aka.ms/ci-fix.