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

Empty siteconfig property under Webapp directory #24

Open
jianyunt opened this Issue Oct 22, 2017 · 3 comments

Comments

Projects
None yet
2 participants
@jianyunt
Contributor

jianyunt commented Oct 22, 2017

A user reported:

From Thom Schumacher
When viewing web applications in my subscription I the property for SiteConfig is empty. I would think that that would be the same value as:
Get-AzureRmWebAppSlot -name webapp -ResourceGroupName myres -slot ‘production’
In the provider my drivename is AZ.
cd az:\mysub\webapps
(gci *webapp).siteconfig
(gci *webapp).sitename — this is valid and has data

CLoudShell Version

PS Azure:\> dir env:acc_version

ACC_VERSION master_20171006.3

Modules

4.4.0 AzureRM
3.4.0 AzureRM.Profile

@jianyunt

This comment has been minimized.

Show comment
Hide comment
@jianyunt

jianyunt Oct 22, 2017

Contributor

@thom, the WebApp directory under Azure drive is calling Get-AzureRmWebApp. I also can repro it with the following commands. Thanks for reporting it. I opened a github issue to track it.

#SiteConfig is empty
Get-AzureRmWebApp | % {$_.SiteConfig}                                             

# worked properly
Get-AzureRmWebApp -name JianyunBot| % {$_.SiteConfig}              
Contributor

jianyunt commented Oct 22, 2017

@thom, the WebApp directory under Azure drive is calling Get-AzureRmWebApp. I also can repro it with the following commands. Thanks for reporting it. I opened a github issue to track it.

#SiteConfig is empty
Get-AzureRmWebApp | % {$_.SiteConfig}                                             

# worked properly
Get-AzureRmWebApp -name JianyunBot| % {$_.SiteConfig}              
@jianyunt

This comment has been minimized.

Show comment
Hide comment
@jianyunt

jianyunt Oct 23, 2017

Contributor

According to @ahmedelnably and @markcowl, populating SiteConfig is a separate call, which can be seriously expensive and perf hit. For that consideration, Siteconfig is empty object for now. However Azure cmdlet team is willing to consider to allow user opt in to perf hit case such as -Config. See Azure/azure-powershell#4841

Contributor

jianyunt commented Oct 23, 2017

According to @ahmedelnably and @markcowl, populating SiteConfig is a separate call, which can be seriously expensive and perf hit. For that consideration, Siteconfig is empty object for now. However Azure cmdlet team is willing to consider to allow user opt in to perf hit case such as -Config. See Azure/azure-powershell#4841

@crshnbrn66

This comment has been minimized.

Show comment
Hide comment
@crshnbrn66

crshnbrn66 Oct 26, 2017

Thank you for your response and for putting the issue I put on the blog site about this... Look forward to what comes next.
thom

crshnbrn66 commented Oct 26, 2017

Thank you for your response and for putting the issue I put on the blog site about this... Look forward to what comes next.
thom

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment