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

updated confluent readme for input files & removed phone number property #9835

Merged
merged 5 commits into from
Jul 1, 2020

Conversation

ankisho
Copy link
Contributor

@ankisho ankisho commented Jun 13, 2020

MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.

Contribution checklist:

If any further question about AME onboarding or validation tools, please view the FAQ.

ARM API Review Checklist

  • Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
    • adding/removing APIs.
    • adding/removing properties.
    • adding/removing API-version.
    • adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

  • If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
    Please follow the link to find more details on API review process.

@openapi-pipeline-app
Copy link

openapi-pipeline-app bot commented Jun 13, 2020

[Staging] Swagger Validation Report

️✔️BreakingChange [Detail]
 There are no breaking changes. 
️✔️LintDiff [Detail]
 Validation passes for LintDiff. 
️✔️Avocado [Detail]
 Validation passes for Avocado. 
Posted by Swagger Pipeline | How to fix these errors?

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@openapi-sdkautomation
Copy link

openapi-sdkautomation bot commented Jun 13, 2020

azure-sdk-for-python - Release

No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured

@openapi-sdkautomation
Copy link

openapi-sdkautomation bot commented Jun 13, 2020

azure-sdk-for-python-track2 - Release

No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured

@openapi-sdkautomation
Copy link

openapi-sdkautomation bot commented Jun 13, 2020

azure-sdk-for-go - Release

No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured

@openapi-sdkautomation
Copy link

openapi-sdkautomation bot commented Jun 13, 2020

Azure CLI Extension Generation - Release

No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured

@openapi-sdkautomation
Copy link

openapi-sdkautomation bot commented Jun 13, 2020

azure-sdk-for-js - Release

No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured

@openapi-sdkautomation
Copy link

openapi-sdkautomation bot commented Jun 13, 2020

azure-sdk-for-java - Release

No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured

@openapi-sdkautomation
Copy link

openapi-sdkautomation bot commented Jun 13, 2020

Trenton Generation - Release

No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured

@openapi-sdkautomation
Copy link

openapi-sdkautomation bot commented Jun 13, 2020

azure-sdk-for-net - Release

No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured

@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@openapi-assignment-bot openapi-assignment-bot bot added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Jun 15, 2020
@ankisho
Copy link
Contributor Author

ankisho commented Jun 16, 2020

@erich-wang : Could you please review this PR ?

@erich-wang
Copy link
Member

@ankisho , the lable WaitForARMFeedbak was added to ask arm review board to review. Adding pattern to existing parameter is kind of break change for customers, has the change been deployed to production?

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@ankisho
Copy link
Contributor Author

ankisho commented Jun 17, 2020

@ankisho , the lable WaitForARMFeedbak was added to ask arm review board to review. Adding pattern to existing parameter is kind of break change for customers, has the change been deployed to production?

This PR has changes related to removing phone number property. This is breaking change.
right now, this RP is on production but it does not come under private preview yet. This RP is not being used by any of azure end-user. I'm doing internal testing using this RP and Private preview is scheduled for 31st July 2020. I've one more PR with similar changeswith RPaaS team: https://github.com/Azure/azure-rest-api-specs-pr/pull/1449

@erich-wang

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@ankisho
Copy link
Contributor Author

ankisho commented Jun 18, 2020

@erich-wang : Could you please review this PR?

@ankisho
Copy link
Contributor Author

ankisho commented Jun 19, 2020

Could you please help me to review this PR? @erich-wang

@ankisho ankisho changed the title updated confluent readme for input files updated confluent readme for input files & removed phone number property Jun 19, 2020
Copy link
Contributor

@chiragg4u chiragg4u left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are breaking changes in this PR. Please take one of the options

  1. confirm if there is no customers for this version
  2. update the API version
  3. follow Azure Breaking changes approval request form as defined @ Breaking Change Process

@@ -538,8 +538,7 @@
"type": "string"
},
"phoneNumber": {
"description": "Phone number. Validation Pattern: ^(\\+\\d{1,2}\\s)?\\(?\\d{3}\\)?[\\s.-]?\\d{3}[\\s.-]?\\d{4}$",
"pattern": "^(\\+\\d{1,2}\\s)?\\(?\\d{3}\\)?[\\s.-]?\\d{3}[\\s.-]?\\d{4}$",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please review the breaking change. Why is this change required?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change is required as we had discussion with ISV Confluent. We & confluent ISV are decided that phone number is not required for this RP and requested to remove this.

@ankisho
Copy link
Contributor Author

ankisho commented Jun 19, 2020

There are breaking changes in this PR. Please take one of the options

  1. confirm if there is no customers for this version
  2. update the API version
  3. follow Azure Breaking changes approval request form as defined @ Breaking Change Process

This PR has changes related to removing phone number property. This is breaking change.
right now, this RP is in production behind hidden feature flag but it does not come under private preview yet. This RP is not being used by any of azure end-user. I'm doing internal testing using this RP and Private preview is scheduled for 31st July 2020.
I've one more PR with similar changes with RPaaS team: https://github.com/Azure/azure-rest-api-specs-pr/pull/1449

@chiragg4u

Copy link
Contributor

@chiragg4u chiragg4u left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving based as the feature is under testing.

@chiragg4u chiragg4u added Approved-BreakingChange DO NOT USE! OBSOLETE label. See https://github.com/Azure/azure-sdk-tools/issues/6374 ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review and removed Breaking Change Review WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Jun 20, 2020
@ankisho
Copy link
Contributor Author

ankisho commented Jun 20, 2020

Approving based as the feature is under testing.

thanks

@ankisho
Copy link
Contributor Author

ankisho commented Jun 22, 2020

@erich-wang : Could you please prioritize the merge of this PR? This is blocking the ARM template generation task.

@erich-wang
Copy link
Member

@akning-ms, could you please force merge this PR?

@ankisho
Copy link
Contributor Author

ankisho commented Jun 27, 2020

@akning-ms, could you please force merge this PR?

@erich-wang @akning-ms : I have a question about this swagger json. we are currently on private preview stage of RP development. since this repo is a public repo, should we merge this swagger to public repo before public private stage?

@akning-ms
Copy link
Contributor

Hi @ankisho, Normally, for private review. you can just submit PR in azure-rest-api-specs-pr(private repo). but looks your preview version 2020-03-01-preview was already in public repo, this PR is just kind of fix. so you can continue your merge for this version if you want. so let us know your thoughts

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@ankisho
Copy link
Contributor Author

ankisho commented Jun 30, 2020

Hi @ankisho, Normally, for private review. you can just submit PR in azure-rest-api-specs-pr(private repo). but looks your preview version 2020-03-01-preview was already in public repo, this PR is just kind of fix. so you can continue your merge for this version if you want. so let us know your thoughts

Hi @akning-ms , i've some updates regarding this.
since, confluent RP is going for private preview phase now(july 2020 end). we have decided that it'd be good if we can expose the confluent RP schema spec to public from Public preview or GA phase. Hence, i've updated this PR to remove the confluent spec from this public repo. Kindly review.

@erich-wang erich-wang merged commit 553d68e into Azure:master Jul 1, 2020
iscai-msft added a commit to iscai-msft/azure-rest-api-specs that referenced this pull request Oct 5, 2020
…into fix_kv_python_readme

* 'master' of https://github.com/Azure/azure-rest-api-specs: (62 commits)
  fixed track2 generation (Azure#9848)
  Update description for requireGuestProvisionSignal. (Azure#9962)
  Inherent Tracked Resource and Proxy Resource from common types (Azure#9866)
  Update pull_request_assignment.yml (Azure#10005)
  Support encryption in transit feature: Add a property when creating a cluster (Azure#9894)
  updated confluent readme for input files & removed phone number property (Azure#9835)
  Update compute readme.python.md (Azure#9999)
  [Hub Generated] Review request for Microsoft.Billing to add version preview/2019-10-01-preview (Azure#9815)
  Fixed the bad output-folder (Azure#9992)
  Add preview APIs for deploying Azure machine learning services (Azure#9592)
  Rename vmware to avs in go SDK (Azure#9903)
  Add api-version 2020-06-01 of compute for go SDK (Azure#9983)
  Added 2020-06-01 API version for Microsoft.AppConfiguration. (Azure#9976)
  separated different error responses (Azure#8881)
  PersonalDesktopAssignmentType optional (Azure#9988)
  Feature/alshulma/update stable version (Azure#8884)
  update error code to use PascalCase to be syned with the library (Azure#8329)
  CosmosDB - Changes for adding PITR workflow APIs (Azure#9897)
  update the lva version and few C# autorest parameters (Azure#9990)
  add cli codegen readme files (Azure#9980)
  ...
00Kai0 pushed a commit to 00Kai0/azure-rest-api-specs that referenced this pull request Oct 12, 2020
…rty (Azure#9835)

* updated confluent readme for input files

* Removed phone number validation

* Removed phone number property

* updated provision state

* Removing preview version from Azure public repo
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Approved-BreakingChange DO NOT USE! OBSOLETE label. See https://github.com/Azure/azure-sdk-tools/issues/6374 ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants