New PowerBI Dedicated module #5010

selasagi · 2017-11-19T13:40:22Z

Description

This checklist is used to make sure that common guidelines for a pull request are followed. You can find a more complete discussion of PowerShell cmdlet best practices here.

I have read the contribution guidelines.
If changes were made to any cmdlet, the XML help was regenerated using the platyPSHelp module.
If any large changes are made to a service, they are reflected in the respective change log.

General Guidelines

Title of the pull request is clear and informative.
There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.
The pull request does not introduce breaking changes (unless a major version change occurs in the assembly and module).

Testing Guidelines

Pull request includes test coverage for the included changes.
PowerShell scripts used in tests should do any necessary setup as part of the test or suite setup, and should not use hard-coded values for locations or existing resources.

Cmdlet Signature Guidelines

New cmdlets that make changes or have side effects should implement ShouldProcess and have SupportShouldProcess=true specified in the cmdlet attribute. You can find more information on ShouldProcess here.
Cmdlet specifies OutputType attribute if any output is produced - if the cmdlet produces no output, it should implement a PassThru parameter.

Cmdlet Parameter Guidelines

Parameter types should not expose types from the management library - complex parameter types should be defined in the module.
Complex parameter types are discouraged - a parameter type should be simple types as often as possible. If complex types are used, they should be shallow and easily creatable from a constructor or another cmdlet.
Cmdlet parameter sets should be mutually exclusive - each parameter set must have at least one mandatory parameter not in other parameter sets.

cormacpayne

@selasagi some comments to take a look at.

In addition, there are a few additional things that need to be done.

(1) There are a few other files missing that you'll need in your project, such as a ChangeLog.md, documentation folder containing the breaking change markdown files, etc. You can check out the PowerBIEmbedded project as a guide to the files you'll need.

(2) You will need to regenerate the .wxi file so your module is a part of the installer. You can follow this guide for more information on how to do so.

(3) In order for your tests to run, you will need to add an entry for your test dll in the TestMappings.json file.

(4) You will need to deprecate the AzureRM.PowerBIEmbedded module. To do so, you will want to add a warning at the beginning of each cmdlet execution stating that the AzureRM.PowerBIEmbedded module will be deprecated in an upcoming breaking change release, and that users should use the AzureRM.PowerBI module instead.

cormacpayne · 2017-11-21T21:17:31Z

src/ResourceManager/PowerBIDedicated/AzureRM.PowerBIDedicated.psd1

+# ProcessorArchitecture = ''
+
+# Modules that must be imported into the global environment prior to importing this module
+RequiredModules = @(@{ModuleName = 'AzureRM.Profile'; ModuleVersion = '3.4.0'; })


@selasagi this should be in-sync with the latest version of AzureRM.Profile, which is 4.0.0

cormacpayne · 2017-11-21T21:17:55Z

src/ResourceManager/PowerBIDedicated/AzureRM.PowerBIDedicated.psd1

+# RootModule = ''
+
+# Version number of this module.
+ModuleVersion = '1.0.0'


@selasagi is this service in public preview? If so, then this should release as 0.1.0

sorry.. GA so I leave the version 1.0.0

cormacpayne · 2017-11-21T21:18:07Z

src/ResourceManager/PowerBIDedicated/AzureRM.PowerBIDedicated.psd1

+Copyright = '� Microsoft Corporation. All rights reserved.'
+
+# Description of the functionality provided by this module
+Description = 'Microsoft Azure PowerShell - PowerBI Embedded Capacity'


@selasagi please change this description

cormacpayne · 2017-11-21T22:23:34Z

src/ResourceManager/PowerBIDedicated/AzureRM.PowerBIDedicated.psd1

+FunctionsToExport = @()
+
+# Cmdlets to export from this module, for best performance, do not use wildcards and do not delete the entry, use an empty array if there are no cmdlets to export.
+CmdletsToExport = 'Resume-AzureRmPowerBIEmbeddedCapacity', 


@selasagi should these cmdlets have the prefix AzureRmPowerBIDedicated, or is AzureRmPowerBIEmbedded the correct prefix?

AzureRmPowerBIEmbeddedCapacity

cormacpayne · 2017-11-21T22:25:46Z

src/ResourceManager/PowerBIDedicated/AzureRM.PowerBIDedicated.psd1

+RequiredModules = @(@{ModuleName = 'AzureRM.Profile'; ModuleVersion = '3.4.0'; })
+
+# Assemblies that must be loaded prior to importing this module
+# RequiredAssemblies = @()


@selasagi uncomment this field and put your management SDK dll in this list (i.e., .\Microsoft.Azure.Management.PowerBIDedicated.dll)

cormacpayne · 2017-11-21T23:23:52Z

src/ResourceManager/PowerBIDedicated/Commands.PowerBIDedicated/Properties/AssemblyInfo.cs

+// set of attributes. Change these attribute values to modify the information
+// associated with an assembly.
+[assembly: AssemblyTitle("Commands.PowerBIDedicated")]
+[assembly: AssemblyDescription("")]


@selasagi please fill in as much information as you can. You can use the AssemblyInfo.cs file in Compute's project as an example

cormacpayne · 2017-11-21T23:25:34Z

...anager/PowerBIDedicated/Commands.PowerBIDedicated/help/Get-AzureRmPowerBIEmbeddedCapacity.md

+Administrator          : {{[email protected]}}
+State                  : Succeeded
+ProvisioningState      : Succeeded
+Id                     : /subscriptions/78e47976-009f-4d4a-a961-6046cdabf459/resourceGroups/testRG/providers/Microsoft.PowerBIDedicated/capacities/testcapacity


@selasagi not sure if you mind this subscription id being publicly visible in the example

cormacpayne · 2017-11-21T23:28:34Z

...anager/PowerBIDedicated/Commands.PowerBIDedicated/help/Get-AzureRmPowerBIEmbeddedCapacity.md

+## PARAMETERS
+
+### -DefaultProfile
+The credentials, account, tenant, and subscription used for communication with azure.```yaml


@selasagi this is a bug in the platyPS module - you will need to move the ```yaml string at the end of this line to a line by itself. Other parameters in this file follow the correct model. Please check all other markdown files for instances of this trailing ```yaml string in parameter descriptions

cormacpayne · 2017-11-21T23:29:22Z

src/ResourceManager/PowerBIDedicated/Commands.PowerBIDedicated/packages.config

@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="utf-8"?>
+<packages>
+  <package id="Microsoft.Bcl" version="1.1.10" targetFramework="net452" />


@selasagi you will need to add your management SDK to this file, and you can go ahead and remove all of the other references found in this file.

cormacpayne · 2017-11-21T23:33:49Z

src/ResourceManager/PowerBIDedicated/AzureRM.PowerBIDedicated.psd1

@@ -0,0 +1,132 @@
+#
+# Module manifest for module 'PSGet_AzureRM.PowerBIDedicated'


@selasagi sent another email about changing the name of this module to AzureRM.PowerBI

cormacpayne

@selasagi more comments to take a look at

cormacpayne · 2017-11-28T17:13:07Z

src/ResourceManager/PowerBI/ChangeLog.md

+-->
+## Current Release
+
+## Version 1.0.0


@selasagi please remove the ## Version 1.0.0 header and move the below information to be under the ## Current Release header

cormacpayne · 2017-11-28T17:17:20Z

src/ResourceManager/PowerBI/Commands.PowerBI/Commands.PowerBI.csproj

+    <DelaySign>true</DelaySign>
+    <SignAssembly>true</SignAssembly>
+    <AssemblyOriginatorKeyFile>MSSharedLibKey.snk</AssemblyOriginatorKeyFile>
+    <DelaySign>true</DelaySign>


@selasagi looks like you repeated an entry for <SignAssembly>, <AssemblyOriginatorKeyFile>, and <DelaySign>

thanks. fixed

@selasagi looks like this is still an issue

cormacpayne · 2017-11-28T17:22:37Z

src/ResourceManager/PowerBI/Commands.PowerBI/Commands/GetAzureRmPowerBIEmbeddedCapacity.cs

+            HelpMessage = "Name of resource group under which the user want to retrieve the capacity.")]
+        [Parameter(
+            ParameterSetName = CapacityParameterSet,
+            Mandatory = false,


@selasagi ResourceGroupName should be mandatory in the parameter set with Name

Name can go also without ResourceGroupName

cormacpayne · 2017-11-28T17:24:32Z

src/ResourceManager/PowerBI/Commands.PowerBI/Commands/GetAzureRmPowerBIEmbeddedCapacity.cs

+            {
+                // List all capacities in given resource group if avaliable otherwise all capacities in the subscription
+                var list = PowerBIClient.ListCapacities(ResourceGroupName);
+                list.ForEach(capacity => WriteObject(capacity));


@selasagi for consistency, I would recommend changing this to WriteObject(list, true), which will enumerate the objects in the list for you and write them to the output stream

cormacpayne · 2017-11-28T17:26:34Z

src/ResourceManager/PowerBI/Commands.PowerBI/Commands/GetAzureRmPowerBIEmbeddedCapacity.cs

+{
+    [Cmdlet(VerbsCommon.Get, "AzureRmPowerBIEmbeddedCapacity"),
+        OutputType(typeof(List<PSDedicatedCapacity>))]
+    public class GetAzurePowerBIEmbeddedCapacity : PowerBICmdletBase


@selasagi the naming of these cmdlets still confuses me - you are receiving a DedicatedCapacity object from the server and transforming it into a PSDedicatedCapacity object, but the cmdlet is called Get-AzureRmPowerBIEmbeddedCapacity instead of Get-AzureRmPowerBIDedicatedCapacity. I was under the impression that PowerBIEmbedded objects are separate from PowerBIDedicated objects.

PSDedicatedCapacity changed to PSPowerBIEmbeddedCapacity

cormacpayne · 2017-11-28T17:38:12Z

src/ResourceManager/PowerBI/Commands.PowerBI/Commands/SuspendAzureRmPowerBIEmbeddedCapacity.cs

+
+        public override void ExecuteCmdlet()
+        {
+            string capacityName = string.Empty;


@selasagi same comment about assigning this to Name and removing the if-statement

cormacpayne · 2017-11-28T17:39:24Z

src/ResourceManager/PowerBI/Commands.PowerBI/Commands/TestAzureRmPowerBIEmbeddedCapacity.cs

+            Mandatory = false,
+            HelpMessage = "Name of resource group under which want to test the capacity.")]
+        [ValidateNotNullOrEmpty]
+        public string ResourceGroupName { get; set; }


@selasagi what value does ResourceGroupName provide if Name is unique?

cormacpayne · 2017-11-28T17:45:28Z

src/ResourceManager/PowerBI/Commands.PowerBI/Commands/UpdateAzureRmPowerBIEmbeddedCapacity.cs

+
+namespace Microsoft.Azure.Commands.PowerBI
+{
+    [Cmdlet(VerbsData.Update, "AzureRmPowerBIEmbeddedCapacity", SupportsShouldProcess = true), 


@selasagi same comment about DefaultParameterSetName

cormacpayne · 2017-11-28T17:45:46Z

src/ResourceManager/PowerBI/Commands.PowerBI/Commands/UpdateAzureRmPowerBIEmbeddedCapacity.cs

+
+        public override void ExecuteCmdlet()
+        {
+            string capacityName = string.Empty;


@selasagi same comment about setting this to Name and removing the below if-statement

cormacpayne · 2017-11-28T17:47:11Z

src/ResourceManager/PowerBI/Commands.PowerBI/Models/PSDedicatedCapacity.cs

+        {
+            get
+            {
+                return _capacity.Sku.Name;


@selasagi for Sku and Tier properties, should we be null-checking _capacity.Sku?

cormacpayne · 2017-12-02T00:09:53Z

src/ResourceManager/PowerBI/Commands.PowerBI/Commands/NewAzureRmPowerBIEmbeddedCapacity.cs

+            Mandatory = true,
+            HelpMessage = "Azure region where the capacity should be created.")]
+        [ValidateNotNullOrEmpty]
+        public string Location { get; set; }


@selasagi please consider adding the LocationCompleter for your creation scenarios that have a Location parameter: https://github.com/Azure/azure-powershell/wiki/PowerShell-Cmdlet-Design-Guidelines#location-completer

This will allow users to tab through valid locations in which they can create the given resource (by using the resource type to determine valid locations)

added. thanks

cormacpayne · 2017-12-02T00:16:35Z

@selasagi two more comments:

(1) Please add the documentation folder to the root of your project and add the two corresponding files in there. This will help prepare for any breaking change that you might have in the future for your module.

(2) Are you going to deprecate the AzureRM.PowerBIEmbedded project and module and move the cmdlets into the new AzureRM.PowerBI module?

…module

…ershell

cormacpayne

@selasagi some additional comments that need to be resolved

cormacpayne · 2017-12-05T02:36:53Z

src/ResourceManager.ForRefactoringOnly.sln

@@ -1687,6 +1687,30 @@ Global
 		{8E5612F5-4F26-49CA-B9AC-67A4C1DB74F3}.Release|x64.Build.0 = Release|Any CPU
 		{8E5612F5-4F26-49CA-B9AC-67A4C1DB74F3}.Release|x86.ActiveCfg = Release|Any CPU
 		{8E5612F5-4F26-49CA-B9AC-67A4C1DB74F3}.Release|x86.Build.0 = Release|Any CPU
+		{9056F1E3-0B1D-46CA-A435-F1E9AAE6DCC0}.Debug|Any CPU.ActiveCfg = Debug|Any CPU


@selasagi are the changes in this file still necessary?

sorry.. this one belong to Commands.AnalysisServices.Test.csproj. shouldn't remove

cormacpayne · 2017-12-05T02:37:32Z

src/ResourceManager/PowerBIEmbedded/ChangeLog.md

@@ -19,36 +19,19 @@
 -->
 ## Current Release

-## Version 4.0.0


@selasagi please revert the deletions made to this file - the new content you are adding can remain under the ## Current Release header

cormacpayne · 2017-12-05T02:37:55Z

src/ResourceManager/PowerBIEmbedded/AzureRM.PowerBIEmbedded.psd1

@@ -12,7 +12,7 @@
 # RootModule = ''

 # Version number of this module.
-ModuleVersion = '4.0.0'
+ModuleVersion = '5.0.0'


@selasagi please revert this version bump - we will handle bumping the versions during the release

cormacpayne · 2017-12-05T02:38:20Z

src/ResourceManager/PowerBIEmbedded/AzureRM.PowerBIEmbedded.psd1

@@ -112,8 +120,7 @@ PrivateData = @{
        # IconUri = ''

        # ReleaseNotes of this module
-        ReleaseNotes = '* Add support for online help
-    - Run Get-Help with the -Online parameter to open the online help in your default Internet browser'
+        ReleaseNotes = '* Add support for PowerBI Embedded Capacity'


@selasagi please revert this change to the release notes - we will handle updating this section during the release using our tooling

cormacpayne · 2017-12-05T02:38:35Z

src/ResourceManager/PowerBI/AzureRM.PowerBI.psd1

@@ -0,0 +1,132 @@
+#


@selasagi can this file be remove? I thought the cmdlets were being shipped with AzureRM.PowerBIEmbedded

cormacpayne · 2017-12-05T02:43:21Z

src/ResourceManager/PowerBIEmbedded/Commands.PowerBI.Test/Commands.PowerBI.Test.csproj

@@ -0,0 +1,229 @@
+<?xml version="1.0" encoding="utf-8"?>


@selasagi any reason you are creating separate cmdlet and test projects for the new cmdlets? Why can't everything be contained in Commands.PowerBIEmbedded.Test and Commands.Management.PowerBI?

I prefer to leave it separate because it will be easier later to remove the commands and the tests of the WorkspaceCollection

cormacpayne · 2017-12-05T02:47:07Z

...rceManager/PowerBIEmbedded/Commands.PowerBI/Commands/ResumeAzureRmPowerBIEmbeddedCapacity.cs

+                if (PassThru.IsPresent)
+                {
+                    // Update the capacity current state 
+                    if (!PowerBIClient.TestCapacity(resourceGroupName, capacityName, out capacity))


@selasagi why is this second TestCapacity call being made when PassThru is provided? Shouldn't it be made regardless of whether or not the user wants output?

If output required, I want that the output capacity state will be updateed/synced

cormacpayne · 2017-12-05T02:47:19Z

...ceManager/PowerBIEmbedded/Commands.PowerBI/Commands/SuspendAzureRmPowerBIEmbeddedCapacity.cs

+                if (PassThru.IsPresent)
+                {
+                    // Update the capacity current state 
+                    if (!PowerBIClient.TestCapacity(resourceGroupName, capacityName, out capacity))


@selasagi same comment

cormacpayne · 2017-12-05T02:48:35Z

tools/AzureRM/AzureRM.psd1

@@ -87,6 +87,7 @@ RequiredModules = @(@{ModuleName = 'AzureRM.Profile'; RequiredVersion = '4.0.0';
               @{ModuleName = 'AzureRM.Network'; RequiredVersion = '5.0.0'; }, 
               @{ModuleName = 'AzureRM.NotificationHubs'; RequiredVersion = '4.0.0'; }, 
               @{ModuleName = 'AzureRM.OperationalInsights'; RequiredVersion = '4.0.0'; }, 
+               @{ModuleName = 'AzureRM.PowerBI'; RequiredVersion = '1.0.0'; }, 


@selasagi same comment - I thought the cmdlets would be shipped with AzureRM.PowerBIEmbedded?

cormacpayne

@selasagi a few more comments. Also, are you still deprecating the existing workspace cmdlets in the future? If so, then you should add an Obsolete attribute on each of the cmdlets so users will know that they should use the new cmdlets you are adding moving forward.

cormacpayne · 2017-12-06T16:30:46Z

src/ResourceManager/PowerBIEmbedded/ChangeLog.md

+    - Modifies an instance of PowerBI Embedded Capacity
+
+-## Version 4.0.0


@selasagi looks like these headers have a - character in front of them, which is affecting how the markdown is being rendered

cormacpayne · 2017-12-06T16:31:20Z

setup/azurecmdfiles.wxi

@@ -885,6 +885,9 @@
                        <Component Id="cmpA7B72722B1AC91C0B6B117CEAB00E3C0" Guid="*">
                            <File Id="fil40386C22E607E953293F5632EAC6393E" KeyPath="yes" Source="$(var.sourceDir)\ResourceManager\AzureResourceManager\AzureRM.PowerBIEmbedded\Microsoft.Azure.Commands.Management.PowerBIEmbedded.dll-Help.xml" />
                        </Component>
+                        <Component Id="cmp20C58BA5A8D7263E84BE2BCB10783E8A" Guid="*">


@selasagi the .wxi file should be regenerated since you are adding a couple new assemblies to the PowerBI project

cormacpayne · 2017-12-06T16:40:21Z

src/ResourceManager/PowerBIEmbedded/Commands.PowerBI/Models/CapacitySku.cs

@@ -0,0 +1,24 @@
+using System;


@selasagi this file is missing a license header

cormacpayne · 2017-12-06T16:41:05Z

src/ResourceManager/PowerBIEmbedded/Commands.PowerBI/Properties/AssemblyInfo.cs

@@ -0,0 +1,36 @@
+using System.Reflection;


@selasagi this file is missing a license header

cormacpayne · 2017-12-06T16:41:34Z

src/ResourceManager/PowerBIEmbedded/Commands.PowerBI/Properties/AssemblyInfo.cs

+// You can specify all the values or you can default the Build and Revision Numbers 
+// by using the '*' as shown below:
+// [assembly: AssemblyVersion("1.0.*")]
+[assembly: AssemblyVersion("1.0.0.0")]


@selasagi both AssemblyVersion and AssemblyFileVersion should match the module version of AzureRM.PowerBIEmbedded

fixed in commands & tests projects

cormacpayne · 2017-12-07T06:33:08Z

On-demand: https://azuresdkci.westus2.cloudapp.azure.com/job/powershell-demand/260/

cormacpayne · 2017-12-07T17:42:05Z

Sign job: https://azuresdkci.westus2.cloudapp.azure.com/job/powershell-sign/41/

Add new PowerBI Dedicated module

eb16f94

azuresdkci added the needs-review label Nov 19, 2017

azuresdkci assigned cormacpayne Nov 19, 2017

selasagi and others added 2 commits November 19, 2017 21:40

Help fixes

7e25a99

Merge branch 'preview' into pbi-dedicated

75c022c

cormacpayne suggested changes Nov 21, 2017

View reviewed changes

cormacpayne added needs-revision and removed needs-review labels Nov 21, 2017

cormacpayne assigned selasagi and unassigned cormacpayne Nov 21, 2017

selasagi added 3 commits November 27, 2017 10:36

Add new PowerBI module

46658c9

fix AzureRM.psm1

e64f631

Fix parameters and help files

0580254

cormacpayne added needs-review and removed needs-revision labels Nov 27, 2017

cormacpayne assigned cormacpayne and unassigned selasagi Nov 27, 2017

selasagi added 2 commits November 28, 2017 11:35

Fix help files and Get cmdlet

24d8938

Fix json test file

1bfae1e

cormacpayne suggested changes Nov 28, 2017

View reviewed changes

cormacpayne added needs-revision and removed needs-review labels Nov 28, 2017

cormacpayne assigned selasagi and unassigned cormacpayne Nov 28, 2017

PR fixes

9021d4e

cormacpayne added needs-review and removed needs-revision labels Nov 29, 2017

cormacpayne assigned cormacpayne and unassigned selasagi Nov 29, 2017

Merge branch 'preview' into pbi-dedicated

fc77f28

cormacpayne reviewed Dec 2, 2017

View reviewed changes

cormacpayne added needs-revision and removed needs-review labels Dec 2, 2017

cormacpayne assigned selasagi and unassigned cormacpayne Dec 2, 2017

selasagi added 2 commits December 3, 2017 16:55

Move PowerBI EMbedded capacity cmdlets under AzureRM.PowerBIEmbedded …

a66ba88

…module

Merge branch 'pbi-dedicated' of https://github.com/selasagi/azure-pow…

4511090

…ershell

markcowl assigned cormacpayne Dec 4, 2017

cormacpayne suggested changes Dec 5, 2017

View reviewed changes

cormacpayne removed their assignment Dec 5, 2017

PR fixs

60212d4

markcowl changed the base branch from preview to release-5.1.0 December 6, 2017 02:30

cormacpayne suggested changes Dec 6, 2017

View reviewed changes

Fix after PR

8650035

maddieclayton assigned cormacpayne and unassigned selasagi Dec 7, 2017

maddieclayton added needs-review and removed needs-revision labels Dec 7, 2017

cormacpayne approved these changes Dec 7, 2017

View reviewed changes

cormacpayne merged commit 014755f into Azure:release-5.1.0 Dec 7, 2017

		@@ -0,0 +1,132 @@
		#
		# Module manifest for module 'PSGet_AzureRM.PowerBIDedicated'

		- Modifies an instance of PowerBI Embedded Capacity

		-## Version 4.0.0

New PowerBI Dedicated module #5010

New PowerBI Dedicated module #5010

Uh oh!

Conversation

selasagi commented Nov 19, 2017 • edited by azuresdkci Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

Uh oh!

cormacpayne left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

cormacpayne left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

selasagi commented Nov 19, 2017 •

edited by azuresdkci

Loading