A collection of fuctions to simplify and facilitate common tasks that are required for automated deployments to Azure using a combinatin of PowerShell scripts and ARM templates.
The following features are implemented as functions of this module. Please note that the "Az" module is a required dependency for this module.
1. Create a new script header for console and log output.
2. Install the required modules from https://powershellgallery.com and import them into the current session.
3. Remove the legacy AzureRM module from the current system.
4. Create a new DSC artificats archive for uploading and staging to an Azure storage account.
5. Authenticate to and set the context for a specified Azure Subscription
6. Specify a fully qualified domain name of the Acitive Directory Domain Services domain to be built in Azure when the IaaS domain controllers are deployed.
7. Upload ARM Templates and DSC artificats to Azure Storge to stage for deployment
8. Create a random string to use for storage accounts, public IP address DNS lables or log analytics workspace name that require globally unique DNS A records.
9. Associate NSGs to their desired subnets.
10. Creates a random password for a credential to create and log into a virtual machine in Azure.
11. Installs a specific version of the Az.Storage module (2.1.0) due to a breaking change with later versions when uploading artifacts to blob storage.
List of software quality issues with the number of affected components.
category ALL
Policies
Info
Category
Problem
Software developers use programming and design knowledge to build reusable software components. Software components are the basic building blocks for modern applications. Software consumed by an enterprise consists of hundreds, and sometimes even thousands of open source components. Software developers publish components they have authored to public repositories. While a new software project is a welcome addition to the open source community, it is not always prudent to indiscriminately use the latest components when building a commercial application. Irrespective of the software quality, the danger of being the first to try out a new project lies in the fact that the software component may contain novel, currently undetected malicious code. Therefore, it is prudent to review software component behaviors and even try out software component in a sandbox, an environment meant for testing untrusted code.
Prevalence in PowerShell Gallery community
1 packages
found in
Top 100
3 packages
found in
Top 1k
5951 packages
found in
Top 10k
15.55k packages
in community
Next steps
Check the software component behaviors for anomalies.
Consider exploratory software component testing within a sandbox environment.
Consider replacing the software component with a more widely used alternative.
Avoid using this software package until it is vetted as safe.
Problem
Software developers use programming and design knowledge to build reusable software components. Software components are the basic building blocks for modern applications. Software consumed by an enterprise consists of hundreds, and sometimes even thousands of open source components. Software developers publish components they have authored to public repositories. While a new software project is a welcome addition to the open source community. it is not always prudent to indiscriminately use the latest components when building a commercial application. Irrespective of the software quality, the danger of using components that are rarely used to build applications lies in the fact that the software component may contain novel, currently undetected malicious code. Therefore, it is prudent to review software component behaviors and even try out software component in a sandbox, an environment meant for testing untrusted code.
Prevalence in PowerShell Gallery community
8 packages
found in
Top 100
474 packages
found in
Top 1k
7926 packages
found in
Top 10k
18.04k packages
in community
Next steps
Check the software component behaviors for anomalies.
Consider exploratory software component testing within a sandbox environment.
Consider replacing the software component with a more widely used alternative.
Avoid using this software package until it is vetted as safe.