iSharkFly-Docs
/
packer-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fix typos in azure-setup.html.md 

Fix a few typos in `azure-setup.html.md`.
This commit is contained in:
Matt Kotsenas 2019-09-16 16:27:05 -07:00 committed by GitHub
parent 8292c7f48f
commit 17d2aa5f93
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
website/source/docs/builders/azure-setup.html.md
View File

@ -9,7 +9,7 @@ sidebar_current: 'docs-builders-azure-setup'
# Authorizing Packer Builds in Azure # Authorizing Packer Builds in Azure
In order to build VMs in Azure Packer needs 6 configuration options to be In order to build VMs in Azure, Packer needs 6 configuration options to be
specified: specified:
- `subscription_id` - UUID identifying your Azure subscription (where billing - `subscription_id` - UUID identifying your Azure subscription (where billing
@ -26,9 +26,9 @@ specified:
- `storage_account` - name of the storage account where your VHD(s) will be - `storage_account` - name of the storage account where your VHD(s) will be
stored stored
-> Behind the scenes Packer uses the OAuth protocol to authenticate against -> Behind the scenes, Packer uses the OAuth protocol to authenticate against
Azure Active Directory and authorize requests to the Azure Service Management Azure Active Directory and authorize requests to the Azure Service Management
API. These topics are unnecessarily complicated so we will try to ignore them API. These topics are unnecessarily complicated, so we will try to ignore them
for the rest of this document.<br /><br />You do not need to understand how for the rest of this document.<br /><br />You do not need to understand how
OAuth works in order to use Packer with Azure, though the Active Directory OAuth works in order to use Packer with Azure, though the Active Directory
terms "service principal" and "role" will be useful for understanding Azure's terms "service principal" and "role" will be useful for understanding Azure's
@ -45,10 +45,10 @@ for Linux based VMs.) Device login is intended for those who are first time
users, and just want to ''kick the tires.'' We recommend the SPN approach if users, and just want to ''kick the tires.'' We recommend the SPN approach if
you intend to automate Packer. you intend to automate Packer.
> Device login is for **interactive** builds, and SPN is **automated** builds. > Device login is for **interactive** builds, and SPN is for **automated** builds.
There are three pieces of information you must provide to enable device login There are three pieces of information you must provide to enable device login
mode. mode:
1. SubscriptionID 1. SubscriptionID
2. Resource Group - parent resource group that Packer uses to build an image. 2. Resource Group - parent resource group that Packer uses to build an image.
@ -111,7 +111,7 @@ you into Azure, name your resources, and export your Packer configuration.
## Manual Setup ## Manual Setup
If you want more control or the script does not work for you, you can also use If you want more control, or the script does not work for you, you can also use
the manual instructions below to setup your Azure account. You will need to the manual instructions below to setup your Azure account. You will need to
manually keep track of the various account identifiers, resource names, and manually keep track of the various account identifiers, resource names, and
your service principal password. your service principal password.