Skip to content

Commit

Permalink
OSS Move updates
Browse files Browse the repository at this point in the history
  • Loading branch information
Willy-Peter Schaub committed Sep 28, 2017
1 parent 2310d25 commit b7c718f
Show file tree
Hide file tree
Showing 4 changed files with 10 additions and 9 deletions.
1 change: 1 addition & 0 deletions .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -23,3 +23,4 @@ org-clock-save.el
emacs-config.el
.vscode
node_modules
/.vs
14 changes: 7 additions & 7 deletions sonarqube-azuresql/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,10 +15,10 @@ Once the deployment is complete you can increase the resources provided to Sonar
[Third Party Notices](https://raw.githubusercontent.com/azure/azure-quickstart-templates/master/sonarqube-azuresql/oss/ThirdPartyNotices.txt)

* * *
####Note:
#### Note:
This Beta release deploys a secure SonarQube installation by default, howevere we invoke a **self-signed** which you will have to replace with a trusted one for production use.

#####Production Certificate
##### Production Certificate
Because CAs provide the various SSL certificate types at different price points, you should start by deciding what type of SSL certificate to buy. To secure a single domain name (**www.contoso.com**), you just need a basic certificate. To secure multiple domain names (**contoso.com** and **www.contoso.com** and **sonarqube.contoso.com**), you need either a wildcard certificate or a certificate with Subject Alternate Name (subjectAltName).+

Once you know which SSL certificate to buy, you submit a Certificate Signing Request (CSR) to a CA. When you get requested certificate back from the CA, you then generate a .pfx file from the certificate. You can perform these steps using the tool of your choice. Here are instructions for the common tools:
Expand All @@ -33,7 +33,7 @@ The approach we used to secure the installation is document in [Running SonarQub

* * *

###Workflow
### Workflow
This template performs the following workflow to create the SonarQube installation.
- Deploy an Azure SQL Server database (named in sqDB\_ServerName) into the selected resource group
- Create a SQL database within the Azure SQl Server (named in sqDB\_DBName)
Expand Down Expand Up @@ -66,20 +66,20 @@ This template performs the following workflow to create the SonarQube installati

* * *

###Deployment
### Deployment
To deploy this template simply click the "Deploy to Azure" button above. This will launch the Azure Portal and you will be prompted to provide values for the parameters below.

The deployment in Azure can take up to 30 minutes. At the end of the deployment, SonarQube will be configured to run as a Windows Service on the SonarQube VM. When the SonarQube service starts for the first time, it will configure its database. This can take up to 15 minutes to complete during which time the Azure deployment shows as completed but you still won't be able to reach the SonarQube home page. _Please give SonarQube some time to update._

Once the deployment and configuration have finished you will be able to access your SonarQube by entering its public address into a browser. The address format is:

#####http://[sq\_PublicIP\_DnsPrefix].[AzureRegion].cloudapp.azure.com:9000
##### http://[sq\_PublicIP\_DnsPrefix].[AzureRegion].cloudapp.azure.com:9000
**Ex:** http://my-sonarqube.eastus.cloudapp.azure.com:9000
**Ex: Secure** https://my-sonarqube.eastus.cloudapp.azure.com

* * *

###Parameter Descriptions
### Parameter Descriptions

| Parameter Name | Description | Default value |
|------------------------|--------------------------------|----------------------------------------------------------------------------|--------------------------------|
Expand All @@ -99,7 +99,7 @@ Once the deployment and configuration have finished you will be able to access y

* * *

###Template Visualization
### Template Visualization
![Template visualization](images/visualize.png)

`Tags: SonarQube, SQL`
Expand Down
2 changes: 1 addition & 1 deletion sonarqube-azuresql/oss/License.txt
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@

Azure Resource Manager template for a Secure SonarQube installation

Copyright (c) Microsoft Corporation
Copyright � ALM | DevOps Ranger Contributors
All rights reserved.

MIT License
Expand Down
2 changes: 1 addition & 1 deletion sonarqube-azuresql/oss/ThirdPartyNotices.txt
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ Do Not Translate or Localize

Azure Resource Manager template for a Secure SonarQube installation

This project incorporates third party material from the projects listed below. The original copyright notice and the license under which Microsoft received such third party material are set forth below. Microsoft reserves all other rights not expressly granted, whether by implication, estoppel or otherwise.
This project incorporates third party material from the projects listed below. The original copyright notice and the license under which ALM | DevOps Ranger Contributors received such third party material are set forth below. ALM | DevOps Ranger Contributors reserve all other rights not expressly granted, whether by implication, estoppel or otherwise.


1. cSecurityOptions (https://github.com/ChrisAWalker/cSecurityOptions)
Expand Down

0 comments on commit b7c718f

Please sign in to comment.