/ARMExplorer

Azure Resource Explorer
  1. TypeScript 32.3%
  2. C# 32.0%
  3. JavaScript 21.9%
  4. HTML 6.9%
  5. CSS 6.1%
  6. PowerShell 0.8%
TypeScript C# JavaScript HTML CSS PowerShell
Find file
Latest commit 425949c Nov 8, 2016 @ahmelsayed ahmelsayed Only add items to search collection if request was successful.
Permalink
Failed to load latest commit information.
App_Data Add latest network json spec Oct 25, 2016
App_Start Added global search function Mar 11, 2015
Content Add status icons for deployments/operations Feb 18, 2016
Controllers Only add items to search collection if request was successful. Nov 8, 2016
Images adding August API version, Adding ARM Explorer Icon, Adding Documenta… Aug 20, 2015
Modules Some fixes for running explorer locally Apr 10, 2015
Properties Renaming to ARMExplorer and moving to projectkudu Jan 31, 2015
Telemetry Some fixes for running explorer locally Apr 10, 2015
Tools Make the provider list utf8 instead of utf16 Sep 29, 2016
ng changing Powershell Cmdlet to list collection from find-resource to g… Jul 21, 2016
raw fix assuming that we are running in /manage subapp Feb 28, 2015
ref Remove hardcoded referenced to hydra specs. Fixes #11 Feb 21, 2015
.gitattributes adding git attributes to handle json as text files Sep 29, 2016
.gitignore Update gitignore to ignore node_modules Sep 14, 2016
.gitmodules Add specs as submodule Mar 28, 2015
ARMExplorer.csproj fixing typo in ProvidersSpecs folder name Aug 20, 2015
ARMExplorer.sln Adding a solution file back Feb 2, 2015
ApplicationInsights.config fix appInsight config error Jun 3, 2015
Global.asax Renaming to ARMExplorer and moving to projectkudu Jan 31, 2015
Global.asax.cs Support Tenant selection in deep link scenarios, Fixes #45 Apr 10, 2015
LICENSE.txt Add license file Jan 31, 2015
README.md Add compute and network spec links to readme Mar 21, 2016
Web.Debug.config Renaming to ARMExplorer and moving to projectkudu Jan 31, 2015
Web.Release.config Renaming to ARMExplorer and moving to projectkudu Jan 31, 2015
Web.config adding SVG mimeType to be able to show the logo Aug 20, 2015
applicationHost.xdt add xdt file Oct 17, 2014
favicon.ico adding August API version, Adding ARM Explorer Icon, Adding Documenta… Aug 20, 2015
index.html Fixed typo on error message when clicking on PUT Aug 9, 2016
packages.config Update AppInsights to 0.17 Jun 3, 2015

README.md

ARMExplorer

This project has dependencies on OAuth authentication.

Instructions

  1. Clone this repository to your local drive.
  2. Open ARMExplorer.sln with VS 2012+ and compile.

Create AAD application

  1. Go to Azure Portal while logged in as an Org ID (i.e. not MSA) and create AAD Application. You may create an application on existing AAD directory or a new directory altogether.
  2. Select Add an application my organization is developing
  3. Enter any name for application name.
  4. Select WEB APPLICATION AND/OR WEB API
  5. Enter https://localhost:44306/ as SIGN ON URL
  6. For APP ID URL, enter something like https://davidebboslingshot.onmicrosoft.com/.
  7. Once created, click CONFIGURE tab
  8. On Permission to other applications, add Windows Azure Service Management API and check Access Azure Service Management for Delegated Permissions and save.

Fix AADClientId and AADClientSecret in codes

  1. Copy CLIENT ID and paste it in this line, replacing Environment.GetEnvironmentVariable("AADClientId").
  2. On Keys section, create a client secret. Copy the key and paste it in the same file, replacing Environment.GetEnvironmentVariable("AADClientSecret").

Test with localhost 1. In VS, make Slingshot.Api the starter project. The RedirectionSite project can be ignored. 1. Starting running it in the debugger (F5). 1. In browser, it should redirect to login page. 1. Enter AAD account and password. Note: try account that is not in the same directly as the application. Note: currently this does not work with MSA account. 1. You should be prompt with OAuth allow/deny page, do accept it.

Test ARM apis

  1. https://localhost:44306/api/token - show current token details.
  2. https://localhost:44306/api/tenants - show all tenants (AAD directory) user belongs to.
  3. and so on..

Test with Azure Websites

  1. Create Azure Websites with local git publishing enabled
  2. Add the site https url as the reply URL for AAD application
  3. Deploy the website by pushing the repository
  4. Set AADClientID and AADClientSecret appSettings
  5. To test, simply browse to the website and append the query string "?repository="

Adding Swagger based specs

Swagger files can be found on https://github.com/Azure/azure-rest-api-specs. The raw file for Web Apps is here. Also, compute and network.

cd Tools
npm install
node ConvertSwaggerToExplorerSpecs.js [Path to swagger spec] > [SpecsName].json
cp [SpecsName].json ..\App_Data\JsonSpecs