Skip to content

New cmdlets to create/enter PSSession in remote container app. New cmdlet for getting container continuous deployment url #7307

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

Merged
merged 17 commits into from
Sep 25, 2018

Conversation

vinisoto
Copy link
Contributor

Description

@panchagnula @jvano @MiYanni
This PR replaces this original PR: #7231 due to the original requestor being OOF.

Azure/azure-powershell-cmdlet-review-pr#145

Checklist

@adxsdkps
Copy link
Collaborator

Can one of the admins verify this patch?

@MiYanni
Copy link
Contributor

MiYanni commented Sep 20, 2018

@vinisoto This PR would at least need to be building successfully by EoD today if it has a chance of getting into a preview module release for Ignite.

Copy link
Contributor

@MiYanni MiYanni left a comment

Choose a reason for hiding this comment

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

  • Missing tests for Enter-AzureRmWebAppContainerPSSession and New-AzureRmWebAppContainerPSSession
    • The Enter cmdlet may not have a way to do tests. So, that may be fine to not have. The New cmdlet can definitely have tests.

@vinisoto
Copy link
Contributor Author

@MiYanni yes. Working on it.

@vinisoto
Copy link
Contributor Author

@MiYanni @panchagnula - Any clues on why this test doesn't find the new cmdlet during CI? It is passing locally:

[xUnit.net 00:00:21.87] Microsoft.Azure.Commands.Websites.Test.ScenarioTests.WebAppTests.TestEnableContainerContiniousDeploymentAndGetUrl [FAIL]
Failed Microsoft.Azure.Commands.Websites.Test.ScenarioTests.WebAppTests.TestEnableContainerContiniousDeploymentAndGetUrl
Error Message:
System.Management.Automation.CommandNotFoundException : The term 'Get-AzureRmWebAppContainerContinuousDeploymentUrl' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
Stack Trace:
at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)

@panchagnula
Copy link
Contributor

@vinisoto - for all commands there is a file that maps the AzureRm command to the az command - have you updated this file? I don't remember the name of the file off the top of my head . I would recommend doing that instead of skipping the test - especially since this a new commandlet you are adding

@vinisoto
Copy link
Contributor Author

@panchagnula - Thanks. Found it. Will try that

@vinisoto
Copy link
Contributor Author

@MiYanni regarding tests for New-AzureRmWebAppContainerPSSession We can't write tests for it as it stands now since:

    1. It depends on having a WS-MAN client which may or may not be available in the build machine (there are some open source WS-MAN clients for Linux, but I'm not familiar with the exact configuration of the build machine)
  1. Since it modifies the local machine WSMAN object, in most cases it needs to run elevated.

I propose that we we don't create a test for it right now until we come up with a way to test it properly. In any case, the underlying API (GetPublishingCredentials) that this cmdlet uses is already being tested by Get-AzureRMWebAppContainerContinuousDeploymentUrl

@vinisoto
Copy link
Contributor Author

Adding this issue to track adding tests to New-AzureRmWebAppContainerPSSession

@MiYanni
Copy link
Contributor

MiYanni commented Sep 21, 2018

@azuresdkci Retest this please

@MiYanni
Copy link
Contributor

MiYanni commented Sep 21, 2018

@vinisoto You have static analysis failures to investigate.

@vinisoto
Copy link
Contributor Author

Thanks @MiYanni. I addressed the static analysis failures.

@MiYanni
Copy link
Contributor

MiYanni commented Sep 21, 2018

@azuresdkci Retest this please

@vinisoto
Copy link
Contributor Author

Looks like all the checks have passed now

@MiYanni
Copy link
Contributor

MiYanni commented Sep 22, 2018

@vinisoto The issue is, the main 2 cmdlets, New and Enter are not designed for your primary use case of running them in CloudShell. See the email thread for details.

@MiYanni
Copy link
Contributor

MiYanni commented Sep 24, 2018

@azuresdkci Retest this please

@MiYanni
Copy link
Contributor

MiYanni commented Sep 24, 2018

@azdevxps Retest this please

@vinisoto
Copy link
Contributor Author

Looks like all checks have passed

Copy link
Contributor

@MiYanni MiYanni left a comment

Choose a reason for hiding this comment

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

  • tools/AzureRM/AzureRM.psm1 should not be committed in this PR.

@MiYanni
Copy link
Contributor

MiYanni commented Sep 24, 2018

@vinisoto Also, this cmdlet will be part of the next AzureRM/Az release (10/05). Is that the intent?

@vinisoto
Copy link
Contributor Author

Yes @MiYanni - we would like this cmdlet to be part of the next release.

@vinisoto
Copy link
Contributor Author

@MiYanni would you mind kicking off retesting? (can I do it myself?)

@MiYanni
Copy link
Contributor

MiYanni commented Sep 25, 2018

@azuresdkci Retest this please

@MiYanni MiYanni merged commit 023c914 into Azure:preview Sep 25, 2018
@vinisoto
Copy link
Contributor Author

Thanks @MiYanni for your help and guidance

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