Azure Test Drive

Azure Test Drive enables customers the option to "try before you buy" products found on Azure Marketplace.

We have a full Wiki to walkthrough what a Test Drive is and how to build one!

Below is our ReadMe for a prototype tool to help to develop, test, and debug your own Azure Test Drive ARM template solution.

Azure Test Drive Dev Kit

Installation
Quick Guide
Documentation

Installation

This project uses Node.js and runs on Windows, Mac OS and Linux machines. Please follow the following steps to install the project:

Make sure you have Node.js v6.9.1 or higher. Follow instructions on this page to install or update Node.js.
Clone the repository (or download the latest version):

git clone https://github.com/Azure/AzureTestDrive.git

Install all dependencies:

npm install

Now you can run Dev Kit tools using Node.js:

node test-drive.js [COMMAND] [PARAMETERS]

Quick Guide

Validate

The validate command performs the basic validation on your template, and displays the sample set of parameters which Azure Test Drive will use to instantiate a template.

node test-drive.js validate samples/contoso_simple_package/main-template.json

Output:

Template is valid
Parameters created
{
  "baseUri": {
    "value": "https://aztestdrive.blob.core.windows.net/your-deployment-package/"
  },
  "sessionId": {
    "value": "862b2264-fc3a-4ae1-a9e3-1e9cc2e2f95f"
  },
  "username": {
    "value": "admin41081"
  },
  "password": {
    "value": "UGo5igjz8j"
  }
}

Start Session

The start session command instantiates your template using the specified Azure subscription.

node test-drive.js start settings.json [<session-name>]

Where:

settings.json is a file containing information which is required to instantiate the template.
session-name is an optional session name. You can run multiple sessions in parallel by specifying different session names.

Output:

Session Details created
{
  "publisherId": ...
}
Downloading template: https://...
Template downloaded
Parameters created
{
  "baseUri": ...
}
Session Details saved
Signing in...
Signed in
Creating Resource Group: CloudTry_585f9917ac694989bede259efe941e49
Resource Group created
{
  "id": ...
}
Creating Deployment...
Deployment created
{
  "id": ...
}

Here is the sample settings.json (subscription id, tenant id, app id and app key parameters are not real):

{
  "$schema": "settings-schema.json",
  "publisherId": "contoso",
  "labId": "simple",
  "subscriptionInfo": {
    "subscriptionId": "12c51fe2-f7ee-46c6-8fc4-cc45069e8b97",
    "tenantId": "243d82c9-14d1-439a-91f8-546ec8708148",
    "appId": "313c023c-98bb-4492-ad10-49db39af81e1",
    "appKey": "AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA="
  },
  "location": "westus",
  "deploymentTemplateUri": "https://aztestdrive.blob.core.windows.net/artifacts/contoso/simple/main-template.json",
  "baseUri": "https://aztestdrive.blob.core.windows.net/artifacts/contoso/simple/"
}

Name	Data Type	Comments
publisherId	String	Publisher identifier (lower-case letters, digits and dash character only).
labId	String	Lab identifier (lower-case letters, digits and dash character only).
subscriptionInfo	Object	Target subscription details.
subscriptionId	GUID	Subscription Id.
tenantId	GUID	Tenant Id.
appId	GUID	AD Application Id (see details below).
appKey	String	AD Application password (see details below).
location	String	Target deployment location.
deploymentTemplateUri	Uri	Uri of your deployment template somewhere on the PUBLIC blob storage
baseUri	Uri	Base Uri of your deployment template

Please note, this project, as well as Azure Test Drive, use service principal to access your subscription.

Get Deployment Status

Template deployment is a long-running operation. The get deployment status command displays the status of your deployment.

node test-drive.js status [<session-name>]

Output:

Session Details loaded
{
  "publisherId": ...
}
Signing in...
Signed in
Retrieving Deployment...
Deployment retrieved
{
  "id": ...
}
Deployment Status: Success

Get Deployment Operations

The get deployment operations command displays information about every deployment operation from your template:

node test-drive.js operations [<session-name>]

Output:

Session Details loaded
{
  "publisherId": ...
}
Signing in...
Signed in
Retrieving Deployment Operations...
Deployment Operations retrieved
[
  {
    "id": ...
  },
  ...
]

This information is also available through the Azure Portal.

Stop Session

The stop session command performs a cleanup. Basically, it just deletes the resource group which was used for deployment:

node test-drive.js stop [<session-name>]

Output:

Session Details loaded
{
  "publisherId": ...
}
Signing in...
Signed in
Deleting Resource Group: CloudTry_585f9917ac694989bede259efe941e49
Resource Group scheduled for deletion

Documentation

See Azure Test Drive WIKI for more information.

Is this repo uptodate?

I am working on building an ARM file for a project we are working on (test drive purposes),

I came across this repo to test my template.json, i tried the below command:

node test-drive.js validate ./samples/winvm/template.json

and i got the below error

throw new Error(No metadata nor default value found, parameter name: ${parameterName}"`);
^

Error: No metadata nor default value found, parameter name: vmName"
at createParameter (/home/sisadmin/sis/arm/AzureTestDrive/lib/template-svc.js:41:19)
at /home/sisadmin/sis/arm/AzureTestDrive/lib/template-svc.js:16:9
at /home/sisadmin/sis/arm/AzureTestDrive/node_modules/lodash/lodash.js:4967:15
at baseForOwn (/home/sisadmin/sis/arm/AzureTestDrive/node_modules/lodash/lodash.js:3032:24)
at /home/sisadmin/sis/arm/AzureTestDrive/node_modules/lodash/lodash.js:4936:18
at Function.forEach (/home/sisadmin/sis/arm/AzureTestDrive/node_modules/lodash/lodash.js:9410:14)
at Object.createParameters (/home/sisadmin/sis/arm/AzureTestDrive/lib/template-svc.js:15:7)
at validateTemplate (/home/sisadmin/sis/arm/AzureTestDrive/test-drive.js:95:34)
at Object. (/home/sisadmin/sis/arm/AzureTestDrive/test-drive.js:21:5)
`

Taking this more, this seems on purpose in the testing code, its either to add a default value to our parameters or a type in the metadata section.

I would add a type but the ones in the list doesn't seems to fit my params.

Any idea how to test my arm file for test drive?

azure / azuretestdrive Goto Github PK

azuretestdrive's Introduction

Azure Test Drive

Azure Test Drive Dev Kit

Installation

Quick Guide

Validate

Start Session

Get Deployment Status

Get Deployment Operations

Stop Session

Documentation

azuretestdrive's People

Contributors

Stargazers

Watchers

Forkers

azuretestdrive's Issues

Recommend Projects

Recommend Topics

Recommend Org