fc1327053c
* initial commit that creates the new archetype * added infra baseline to ASE/SQL deployment * added vnet peering module configurations * set app service plan and webapp as generic modules, added ASE orchestration modules to archetype * Fixes to pester tests applied * added baseline archetype * added Nist controls * added new NIST policies * update settings * fixed repeated policy display name * Update Archetype Instance Json with Script Output (#65) * Completed the implementation of the archetype instance update with script outpout * Created script to create / use a subscription and associate it to a new / existing management group * SQL database (#64) * Add files via upload * Delete _README.md * Add files via upload * Delete sql.database.deploy.json * Delete sql.database.parameters.json * Add files via upload * Delete sql.database.azuredevops.ci.yaml * Add files via upload * Add files via upload * Delete git_placeholder.md * Update module.tests.ps1 * Update module.tests.ps1 * added new NIST policies * initial commit that creates the new archetype * added infra baseline to ASE/SQL deployment * added vnet peering module configurations * set app service plan and webapp as generic modules, added ASE orchestration modules to archetype * Fixes to pester tests applied * added baseline archetype * Completed the implementation of the archetype instance update with script outpout * Created script to create / use a subscription and associate it to a new / existing management group * update settings * fixed repeated policy display name * initial commit that creates the new archetype * added infra baseline to ASE/SQL deployment * added vnet peering module configurations * set app service plan and webapp as generic modules, added ASE orchestration modules to archetype * Fixes to pester tests applied * added baseline archetype * Completed the implementation of the archetype instance update with script outpout * Created script to create / use a subscription and associate it to a new / existing management group * initial commit that creates the new archetype * added infra baseline to ASE/SQL deployment * added vnet peering module configurations * set app service plan and webapp as generic modules, added ASE orchestration modules to archetype * Completed the implementation of the archetype instance update with script outpout * Completed the implementation of the archetype instance update with script outpout * Created script to create / use a subscription and associate it to a new / existing management group * initial commit that creates the new archetype * added infra baseline to ASE/SQL deployment * added vnet peering module configurations * set app service plan and webapp as generic modules, added ASE orchestration modules to archetype * added baseline archetype * Completed the implementation of the archetype instance update with script outpout * initial commit that creates the new archetype * added infra baseline to ASE/SQL deployment * added vnet peering module configurations * initial commit that creates the new archetype * set app service plan and webapp as generic modules, added ASE orchestration modules to archetype * added infra baseline to ASE/SQL deployment * added vnet peering module configurations * set app service plan and webapp as generic modules, added ASE orchestration modules to archetype * Completed the implementation of the archetype instance update with script outpout * Resolved a conflict * removed subscription verification * running custom script * cleaned up variables * Tested custom script execution * Updated the subscription name for testing * Check for null subscript and tenant id added * Added debug for pipeline failures * Updated Add-SubscriptionAndTenantIds to run only for archetype configuration * Throw more information when script execution fails * Throw more information when script execution fails * Throw more information when script execution fails * Throw more information when script execution fails * Throw more information when script execution fails * Throw more information when script execution fails * Throw more information when script execution fails * Throw more information when script execution fails * finished NIST Controls * moved baseline configuration to ASE-SQL * fixed common file path reference * updated Shared Services pipeline * updated file name - case sensitive issue * updated validation rg creation * Changed the tenant id and subscription id in New-AzureResourceManagerDeployment to string * added workload baseline pipeline * added ase sql pipeline * fixed invalid subscription id saved to resource state * updated variable name * Reference Functions scope changed to Module Configuration Object (#66) * Initial changes * Completed the implementation * Cleaned up prior to PR submission * adding LandingZone * updated pipeline paths * updated pipeline paths * updated parameters file * correcting case * removed folders * placing files back * delete files * put files back * Fix to resolving reference functions * fixed casing * fixed casing in code * updated modules to Modules in pipeline.yml * Updated config folder name * Updated config folder name * fixed casing * added vpn shared key * finished ASE SQLDB landing zone * added ASE-SQL archetype * replaced hardcoded resource group name * fixed relative path * fixed automation account alias * fixed relative paths * renamed ADDS to ActiveDirectoryDomainServices * fixed onprem vgw name * fixed artifacts storage account name * fixed custom extensions casing * enabled adds deployment * updated on-premises AD information * updated Key Vault name to pass deployment error * fixed bug on resource group creation * updated adds vm name and set pipeline timeout to 0 * updated ADDS address start * updated ADDS name * updated dockerignore * Fixed the pester test failure |
||
---|---|---|
.. | ||
_media | ||
archetypes | ||
extend | ||
reference | ||
setup | ||
understand | ||
use | ||
adoc-file-format.adoc | ||
readme.md |
readme.md
Azure VDC Documentation
Understanding the concepts
These articles will help you understand how the Azure Virtual Datacenter Automation Toolkit works and what it is intended to do.
- Prerequisite Azure knowledge - Resources for understanding the Azure services that the toolkit utilizes.
- Understanding the Automation Toolkit - Explains the important concepts in the toolkit.
- Understanding environment types - Describes the built-in environment types that the toolkit can deploy.
- Common workflow - Covers the typical usage pattern for the tools in the toolkit.
- Roles and permissions - Lists the custom roles that are provided by default in the toolkit.
- Modules - Explains the modules included in the toolkit.
Setting up the toolkit
We recommend using the Docker image provided in this GitHub repository to run the toolkit. However, you can run the toolkit locally if you choose. After getting the toolkit setup, you'll be ready to make your first deployment with the toolkit.
- Run the Docker image (Recommended) - How to setup the toolkit using Docker.
- Run on your local machine - How to setup the toolkit natively.
Usage patterns for the toolkit
This section provides more detail on deploying archetypes and modules with the toolkit.
- Your first deployment - Quick start tutorial for deploying the simulated on-premises archetype.
- General considerations - Items to evaluate before deploying any archetype.
- Creating archetype configuration files - How to prepare an
archetype.json
file.- Common parameters - Parameters used in all archetype configuration files.
- Common workload parameters - Parameters used by workload archetype configuration files.
- Archetype deployment considerations - Items to evaluate that are specific to shared-services and workload environments.
- Validating deployments - How to validate an archetype configuration.
Extending the toolkit
The real power of the toolkit is the ability to create new archetypes and modules to meet your specific needs.
- Creating new modules - How to create a new module.
- Creating new archetypes - How to create a new archetype.
- Using the integration tests - How to run and add new integration tests.
Script Reference
There are four Python scripts provided by the toolkit.
- policy-assignment.py Update subscription policy post-deployment
- role-creation.py Create subscription roles
- subscription.py Create management groups and subscriptions
- vdc.py Deploy archetypes and modules
Archetypes
Be sure to understand the different environment types for archetypes.
- Simulated on-premises environment
- Shared services
- IaaS N-tier architecture
- App Service Environment + SQL Database
- SAP HANA
- Cloudbreak
NOTE: If you are interested in contributing, please note that some of the docs are authored in AsciiDoc (.adoc) and others are Markdown (.md).