Skip to content

Creator (2023-03-01-preview) retirement banners.#30697

Merged
stevemunk merged 2 commits intoAzure:mainfrom
stevemunk:retirement-banner-updates-creator
Sep 24, 2024
Merged

Creator (2023-03-01-preview) retirement banners.#30697
stevemunk merged 2 commits intoAzure:mainfrom
stevemunk:retirement-banner-updates-creator

Conversation

@stevemunk
Copy link
Member

Data Plane API Specification Update Pull Request

🚨🚨🚨 🚨🚨🚨 🚨🚨🚨 🚨🚨🚨 🚨🚨🚨 🚨🚨🚨 🚨🚨🚨 🚨🚨🚨 🚨🚨🚨 🚨🚨🚨
Added retirement banners (to the description fields) to the following deprecated Azure Maps service:

Only changes were to the description fields, should only impact the user docs.

Minor fixes/updates to Creator v2 retirement banners.

🚨🚨🚨 🚨🚨🚨 🚨🚨🚨 🚨🚨🚨 🚨🚨🚨 🚨🚨🚨 🚨🚨🚨 🚨🚨🚨 🚨🚨🚨 🚨🚨🚨

Tip

Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

PR review workflow diagram

Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

spec_pr_review_workflow_diagram

API Info: The Basics

Most of the information about your service should be captured in the issue that serves as your API Spec engagement record.

  • Link to API Spec engagement record issue:

Is this review for (select one):

  • a private preview
  • a public preview
  • GA release

Change Scope

This section will help us focus on the specific parts of your API that are new or have been modified.
Please share a link to the design document for the new APIs, a link to the previous API Spec document (if applicable), and the root paths that have been updated.

  • Design Document:
  • Previous API Spec Doc:
  • Updated paths:

Viewing API changes

For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures

If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
Swagger-Suppression-Process
to get approval.

❔Got questions? Need additional info?? We are here to help!

Contact us!

The Azure API Review Board is dedicated to helping you create amazing APIs. You can read about our mission and learn more about our process on our wiki.

Click here for links to tools, specs, guidelines & other good stuff

Tooling

Guidelines & Specifications

Helpful Links

Getting help

  • First, please carefully read through this PR description, from top to bottom.
  • If you don't have permissions to remove or add labels to the PR, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories
  • To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
  • For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
    and https://aka.ms/ci-fix.
  • If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
    This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
  • If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

@stevemunk stevemunk requested a review from a team as a code owner September 23, 2024 23:22
@stevemunk stevemunk requested review from bexxx and tg-msft and removed request for a team September 23, 2024 23:22
@openapi-pipeline-app
Copy link

openapi-pipeline-app bot commented Sep 23, 2024

Next Steps to Merge

✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge.

@openapi-pipeline-app
Copy link

openapi-pipeline-app bot commented Sep 23, 2024

@stevemunk stevemunk added the PublishToCustomers Acknowledgement the changes will be published to Azure customers. label Sep 24, 2024
@stevemunk stevemunk enabled auto-merge (squash) September 24, 2024 00:17
@stevemunk stevemunk merged commit 532af24 into Azure:main Sep 24, 2024
cheukchuen pushed a commit that referenced this pull request Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

data-plane Maps PublishToCustomers Acknowledgement the changes will be published to Azure customers.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants