Skip to content

Conversation

@mkarmark
Copy link
Contributor

@mkarmark mkarmark commented Jun 11, 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.

@yonzhan yonzhan requested a review from Juliehzl June 12, 2021 00:50
@yonzhan yonzhan requested a review from zhoxing-ms June 12, 2021 00:50
@yonzhan yonzhan added this to the S189 milestone Jun 12, 2021
@yonzhan
Copy link
Collaborator

yonzhan commented Jun 12, 2021

App Service

Copy link
Member

@cgillum cgillum left a comment

Choose a reason for hiding this comment

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

A few commands and questions based on my review of the samples.

Copy link

@ConnorMcMahon ConnorMcMahon left a comment

Choose a reason for hiding this comment

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

Overall I think it looks pretty good! Mostly some nitpicks and logistics questions.

Copy link
Member

@cgillum cgillum left a comment

Choose a reason for hiding this comment

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

A few more nits/questions, but I don't see anything fundamentally blocking. Great work on this!

Copy link

@ConnorMcMahon ConnorMcMahon left a comment

Choose a reason for hiding this comment

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

LGTM!

@mkarmark
Copy link
Contributor Author

@Juliehzl @zhoxing-ms The only CI checks that are failing are the integrated tests for other extensions (not anything I touched). Is there any way to get passed those blockers if we want to release this extension soon?

@Juliehzl
Copy link
Contributor

@Juliehzl @zhoxing-ms The only CI checks that are failing are the integrated tests for other extensions (not anything I touched). Is there any way to get passed those blockers if we want to release this extension soon?

Hi @mkarmark, please merge or rebase your PR with latest main branch.

@mkarmark
Copy link
Contributor Author

#sign-off

@mkarmark
Copy link
Contributor Author

@Juliehzl That worked, thanks! What steps are left for me to merge this PR?

@Juliehzl
Copy link
Contributor

Juliehzl commented Jul 15, 2021

@Juliehzl That worked, thanks! What steps are left for me to merge this PR?

Please resolve conflicts to make CI pass. service name items need to be in alphabetical order

Copy link
Contributor

Choose a reason for hiding this comment

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

what is the reason for this? This will override all the webapp extension commands to not have preview tag - & that is not correct. Please verify & remove.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

so this is a separate extension from the webapps extension and these commands are not preview, so I'm confused how it would override a diff extension commands?

Copy link
Contributor

@panchagnula panchagnula left a comment

Choose a reason for hiding this comment

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

Few comments to address.

@mkarmark mkarmark requested a review from panchagnula July 15, 2021 23:01
Copy link
Contributor

@panchagnula panchagnula left a comment

Choose a reason for hiding this comment

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

A few minor comments. otherwise looks good.

@mkarmark
Copy link
Contributor Author

@Juliehzl @panchagnula my local test generates a recording that uses 2020-10-01 but the test expects api version 2021-04-01. Do you know what I can do to mitigate this error?

@yonzhan
Copy link
Collaborator

yonzhan commented Jul 29, 2021

@panchagnula could you please help above question since Zunli is OOF?

@panchagnula
Copy link
Contributor

@Juliehzl @panchagnula my local test generates a recording that uses 2020-10-01 but the test expects api version 2021-04-01. Do you know what I can do to mitigate this error?

@mkarmark as we discussed pleas wait for @calvinsID to update the CLI extension to use the track 2 SDK version & then re-base. Thanks!

Copy link
Contributor

@panchagnula panchagnula left a comment

Choose a reason for hiding this comment

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

LGTM

@panchagnula panchagnula merged commit 8feab47 into Azure:main Jul 30, 2021
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.

7 participants