Skip to content

[Communication] 1.0.0 release#3216

Merged
kairu-ms merged 1 commit intoAzure:mainfrom
memontic-ms:communication-ga-release
Jul 20, 2021
Merged

[Communication] 1.0.0 release#3216
kairu-ms merged 1 commit intoAzure:mainfrom
memontic-ms:communication-ga-release

Conversation

@memontic-ms
Copy link
Contributor

@memontic-ms memontic-ms commented Apr 1, 2021


This checklist is used to make sure that common guidelines for a pull request are followed.

General Guidelines

  • Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
  • Have you run python scripts/ci/test_index.py -q locally?

For new extensions:

About Extension Publish

There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

@memontic-ms memontic-ms force-pushed the communication-ga-release branch from 633ebe1 to 128d4ab Compare April 1, 2021 11:45
@yonzhan yonzhan requested review from jsntcy, kairu-ms and msyyc April 1, 2021 11:48
@yonzhan yonzhan added this to the S185 milestone Apr 1, 2021
@yonzhan
Copy link
Collaborator

yonzhan commented Apr 1, 2021

Communication

@memontic-ms
Copy link
Contributor Author

Top-level subgroups are now 'service' and 'status'. Not sure if this is intended.

This makes it so that
0.1.0:
az communication list --resource-group "MyResourceGroup"
1.0.0:
az communication service list --resource-group "MyResourceGroup"

@memontic-ms
Copy link
Contributor Author

Need help getting the tests to pass

@yonzhan yonzhan requested a review from qiaozha April 1, 2021 12:34
@yonzhan
Copy link
Collaborator

yonzhan commented Apr 1, 2021

@qiaozha @kairu-ms please help with this PR

@usvoyager usvoyager added the Communication Label for AzureCommunicationServices label Apr 1, 2021
@memontic-ms memontic-ms force-pushed the communication-ga-release branch from 128d4ab to bdd8684 Compare April 7, 2021 20:39
@kairu-ms
Copy link
Contributor

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@yonzhan yonzhan modified the milestones: S185, S186 Apr 27, 2021
@kairu-ms
Copy link
Contributor

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@yonzhan yonzhan modified the milestones: S186, S187 May 12, 2021
@kairu-ms
Copy link
Contributor

@memontic-ms Please rebase your branch on latest master branch.

@memontic-ms memontic-ms force-pushed the communication-ga-release branch from bdd8684 to f387f75 Compare May 27, 2021 02:10
@kairu-ms
Copy link
Contributor

kairu-ms commented Jun 2, 2021

@memontic-ms Please fix test issues.

Comment on lines 15 to 20
Copy link
Contributor

Choose a reason for hiding this comment

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

I think communicationservice has prefix communication which is duplicated with parent command group name. Why not rename it to service as a short?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I don't know what the guidelines for the naming is. I didn't make any customizations since the initial version, so I don't know why this generated differently. What should this look like? How can I get it to generate with the correct command names?

Copy link
Contributor

Choose a reason for hiding this comment

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

Could you please share your swagger link and codegen configuration?

@memontic-ms memontic-ms force-pushed the communication-ga-release branch from f387f75 to 2b30be3 Compare July 8, 2021 08:12
@memontic-ms
Copy link
Contributor Author

I regenerated based on the suggestions from @kairu-ms

This version looks a little better and seems to be following the directives from the readme.
I used a version of the readme.az.md with the changes at memontic-ms/azure-rest-api-specs@40adbb7

The tests are failing unexpectedly and I don't know how to fix them. @kairu-ms please help me try and get the tests to succeeded. I think there are several things wrong. The first thing that goes wrong is a JSON parsing exception.

@memontic-ms memontic-ms force-pushed the communication-ga-release branch from 2b30be3 to c72b4cd Compare July 8, 2021 21:19
@kairu-ms
Copy link
Contributor

kairu-ms commented Jul 15, 2021

@memontic-ms I've created a PR which fix your issues FYI df10f95

@memontic-ms memontic-ms force-pushed the communication-ga-release branch from c72b4cd to 1a1db03 Compare July 19, 2021 21:16
Manually updates:
Test fixes
Add test recordings
Update version number
Update help
Update README
Update HISTORY
@memontic-ms memontic-ms force-pushed the communication-ga-release branch from 5bd929a to 61e4bce Compare July 19, 2021 23:35
@memontic-ms memontic-ms marked this pull request as ready for review July 19, 2021 23:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Communication Label for AzureCommunicationServices

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants