-
Notifications
You must be signed in to change notification settings - Fork 3.3k
AppService: Updating to use the latest version of SDK #11476
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
Conversation
|
@qwordy can you help me figure out what is missing here since i see this error in dependencycheck "{'load_commands': ModuleNotFoundError("No module named 'azure.mgmt.web.web_site_management_client'",)}" |
|
Hi @panchagnula, according to your code change in the PR, you plan to upgrade the azure-mgmt-web to 0.44.0, and I will assume you want to use v2019-08-01 for AppService related commands. Is this you expected? And I am working on MultiAPI support for AppService and I think I can upgrade the api version for you. |
Try |
Got it! |
f60f67c to
00ad011
Compare
|
add to S163. |
|
Hi @panchagnula are you still working on this? |
00ad011 to
ddf20ce
Compare
b0d1dea to
463dc29
Compare
5e5841b to
be764e3
Compare
Is it still this error blocking you? |
I figured out the issue - took some time to debug - but I think I got it now. Couple more failing tests but after that I should be good to go. |
288a0af to
7d2e124
Compare
e2fb1ab to
fd57199
Compare
|
@Juliehzl/ @qwordy this PR is ready except for one test "test_metric_alert_v2_scenario" I am unable to re-record this because the storage_account is missing can one of you help me with this- this is the last piece to get the build working. Thanks a lot! that needs to be re-recorded |
Have you rebase the dev branch recently?
Hi @panchagnula, it is caused by storage service in monitor alert. We will do the change in dev branch and you can pull the latest dev and rebase dev branch when it is ready. |
Sounds good thanks - let me know when the fix is in dev I will pull & rebase. |
you can rebase dev branch now. if there is still problem, feel free to let me know. |
|
@Juliehzl any update on this please? Thanks! |
You can rebase the dev now and re-record for the test. I think it should work now. |
Tried this & still the same error when trying to re-record raise CLIError('{} {}'.format(message, code)) |
fd57199 to
e539052
Compare
This test needs to be re-recoded with this change since this use Appservice plan command the api-version of which has been updated in this PR. Can I disable this test as a part of this, merge these & someone from the core team re-record this once this is in dev? Please let me know - this has been sitting in PR forever. |
|
@Juliehzl please merge this PR by this week. |
|
Hi @panchagnula, can you use |
e539052 to
140ea1f
Compare
…pi support Adding new file Re-recording webjobs tests Adding Yaml files Re-running tests Removing incorrect tests & add new recording Updating requirements files recording Linux test on MAC Adding recording for Identity file Removing reservedInstanceCount since its no longer supported with new API-version PyLint fixes Adding recording for failing tests Adding recording Updating clientFacotory Updating reference to APPService MGMT_Client Fixing linter to find the client_management operations Adding recording Updating to use an api-version that has website_client_management Updating to use 2018-02-01 as the api-version Fixing mock tests after using multi-api SDK support Recording bot tests after webapp sdk update Updating history Recording for failing bot test Fixing history
140ea1f to
ff4d6ad
Compare
haven't checked will take a look. Is there a reason you are checking this? Is there some known issue you are aware of? Thanks! |
|
closing this since this is was covered by #11056 |
Fixes #10476
This checklist is used to make sure that common guidelines for a pull request are followed.
The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).
I adhere to the Command Guidelines.