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

extract SkuTier as seperate definition for common-types/v3.json #15898

Merged
merged 1 commit into from
Sep 22, 2021

Conversation

zhenglaizhang
Copy link
Contributor

@zhenglaizhang zhenglaizhang commented Sep 2, 2021

This is per request from service team (#15662 (comment)) and I did a check on python track2 it's not a breaking change in PR #15876.

And need SDK owners review to check if it's a SDK breaking change

@openapi-workflow-bot
Copy link

Hi, @zhenglaizhang Thanks for your PR. I am workflow bot for review process. Here are some small tips.

  • Please ensure to do self-check against checklists in first PR comment.
  • PR assignee is the person auto-assigned and responsible for your current PR reviewing and merging.
  • For specs comparison cross API versions, Use API Specs Comparison Report Generator
  • If there is CI failure(s), to fix CI error(s) is mandatory for PR merging; or you need to provide justification in PR comment for explanation. How to fix?

  • Any feedback about review process or workflow bot, pls contact swagger and tools team. vsswagger@microsoft.com

    @openapi-workflow-bot
    Copy link

    [Call for Action] To better understand Azure service dev/test scenario, and support Azure service developer better on Swagger and REST API related tests in early phase, please help to fill in with this survey https://aka.ms/SurveyForEarlyPhase. It will take 5 to 10 minutes. If you already complete survey, please neglect this comment. Thanks.

    @openapi-pipeline-app
    Copy link

    openapi-pipeline-app bot commented Sep 2, 2021

    Swagger Validation Report

    ️️✔️BreakingChange succeeded [Detail] [Expand]
    There are no breaking changes.

    ️️✔️LintDiff succeeded [Detail] [Expand]
    Validation passes for LintDiff.
    ️️✔️Avocado succeeded [Detail] [Expand]
    Validation passes for Avocado.
    ️️✔️ModelValidation succeeded [Detail] [Expand]
    Validation passes for ModelValidation.
    ️️✔️SemanticValidation succeeded [Detail] [Expand]
    Validation passes for SemanticValidation.
    ️️✔️Cross-Version Breaking Changes succeeded [Detail] [Expand]
    There are no breaking changes.
    ️️✔️CredScan succeeded [Detail] [Expand]
    There is no credential detected.
    ️️✔️[Staging] SDK Track2 Validation succeeded [Detail] [Expand]
    Validation passes for SDKTrack2Validation
    ️️✔️[Staging] PrettierCheck succeeded [Detail] [Expand]
    Validation passes for PrettierCheck.
    ️️✔️[Staging] SpellCheck succeeded [Detail] [Expand]
    Validation passes for SpellCheck.
    ️️✔️[Staging] Lint(RPaaS) succeeded [Detail] [Expand]
    Validation passes for Lint(RPaaS).
    Posted by Swagger Pipeline | How to fix these errors?

    @openapi-pipeline-app
    Copy link

    openapi-pipeline-app bot commented Sep 2, 2021

    Swagger pipeline restarted successfully, please wait for status update in this comment.

    @forteddyt
    Copy link
    Contributor

    This will address the issue in #15662, so thank you.

    I just wanted to also point out that this same type of change could be applied to the other enum property types, as well. like "type", "origin", "actionType", "createdByType", "lastModifiedByType", "status", and "reason".

    @weidongxu-microsoft
    Copy link
    Member

    @zhenglaizhang Do you need review from ARM?

    @zhenglaizhang
    Copy link
    Contributor Author

    @msyyc @qiaozha @fengzhou-msft @ArcturusZhang could you help take a look from SDK perspective?

    @weidongxu-microsoft
    Copy link
    Member

    One question not related to this change.

    Why use "allOf"?

    "identity": {
    "allOf": [
    {
    "$ref": "#/definitions/Identity"
    }
    ]
    },
    "sku": {
    "allOf": [
    {
    "$ref": "#/definitions/Sku"
    }
    ]
    },
    "plan": {
    "allOf": [
    {
    "$ref": "#/definitions/Plan"
    }
    ]
    }

    @zhenglaizhang
    Copy link
    Contributor Author

    @zhenglaizhang Do you need review from ARM?

    no need to do ARM review,

    @zhenglaizhang
    Copy link
    Contributor Author

    One question not related to this change.

    Why use "allOf"?

    "identity": {
    "allOf": [
    {
    "$ref": "#/definitions/Identity"
    }
    ]
    },
    "sku": {
    "allOf": [
    {
    "$ref": "#/definitions/Sku"
    }
    ]
    },
    "plan": {
    "allOf": [
    {
    "$ref": "#/definitions/Plan"
    }
    ]
    }

    good catch, ref should be better here.

    @zhenglaizhang zhenglaizhang changed the title extract SkuTier as seperate definition for common-types/v2.json extract SkuTier as seperate definition for common-types/v3.json Sep 22, 2021
    @zhenglaizhang
    Copy link
    Contributor Author

    .net/python sdk owners are also ok with this change.

    @zhenglaizhang zhenglaizhang merged commit a62f0a7 into main Sep 22, 2021
    @zhenglaizhang
    Copy link
    Contributor Author

    @forteddyt I merged the PR, so you can try to reference it in v3 common types.json

    Hardell pushed a commit to Hardell/azure-rest-api-specs that referenced this pull request Sep 27, 2021
    LeiWang3 pushed a commit to LeiWang3/azure-rest-api-specs that referenced this pull request Mar 31, 2022
    @JackTn JackTn deleted the extract-SkuTier branch June 16, 2022 00:49
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Labels
    None yet
    Projects
    None yet
    Development

    Successfully merging this pull request may close these issues.

    6 participants