Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

more in-depth quick start guide #1196

Merged
merged 16 commits into from
May 20, 2021
Merged

Conversation

frodopwns
Copy link
Contributor

This guide walks the user through deploying an application using ASO to an AKS cluster pretty much from scratch.

What this PR does / why we need it:
Initial quick start is over simplified.

@frodopwns frodopwns changed the title WIP: more in-depth quick start guide more in-depth quick start guide Jul 9, 2020
Comment on lines 25 to 27
VOTES_APP_INSTANCE_NAME="<alias>" # only alpha numeric
TENANT_ID=""
SUBSCRIPTION_ID=""

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we add instructions on how people can get the values for these variables?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please also add some links that describe what those ID are

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can do!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm adding the instructions for finding them. I'm not sure a quick start for someone completely unfamiliar to Azure is entirely in scope here. Plus, I don't know if MS has a definition listed anywhere.

docs/howto/quickstart.md Outdated Show resolved Hide resolved
docs/howto/quickstart.md Outdated Show resolved Hide resolved
docs/howto/quickstart.md Outdated Show resolved Hide resolved
Copy link

@alsuren alsuren left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I followed this version of the quickstart when setting up my cluster. Worked pretty well. I left a few comments about things that I noticed.

Comment on lines +26 to +27
TENANT_ID=""
SUBSCRIPTION_ID=""
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would be tempted to assume that most people will already be logged into azure, and flip these on their heads.

Maybe tell people to:
az login and az account set -s YOUR_SUBSCRIPTION_ID
at the top, and then:

Suggested change
TENANT_ID=""
SUBSCRIPTION_ID=""
TENANT_ID=$(az account show | jq -r .homeTenantId)
SUBSCRIPTION_ID=$(az account show | jq -r .id)

here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hmm, yes, this looks better to me

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

although....not sure if the windows folks will get this to work in powershell...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

guess since we are already using jq it doesn't matter too much

Copy link

@frigus02 frigus02 Jul 22, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could use --query and --output tsv instead of jq, similar to the other examples in the file:

TENANT_ID=$(az account show --query homeTenantId -o tsv)
SUBSCRIPTION_ID=$(az account show --query id -o tsv)

docs/howto/quickstart.md Outdated Show resolved Hide resolved
docs/howto/quickstart.md Outdated Show resolved Hide resolved
docs/howto/quickstart.md Outdated Show resolved Hide resolved
frodopwns and others added 8 commits July 21, 2020 13:45
Co-authored-by: Sakthi Vetrivel <suvetriv@microsoft.com>
Co-authored-by: Sakthi Vetrivel <suvetriv@microsoft.com>
Co-authored-by: David Laban <alsuren@gmail.com>
Co-authored-by: David Laban <alsuren@gmail.com>
Co-authored-by: David Laban <alsuren@gmail.com>
Co-authored-by: Sakthi Vetrivel <suvetriv@microsoft.com>
@matthchr matthchr requested a review from babbageclunk as a code owner May 19, 2021 17:53
@codecov-commenter
Copy link

Codecov Report

Merging #1196 (947425b) into master (b790d84) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #1196   +/-   ##
=======================================
  Coverage   62.13%   62.13%           
=======================================
  Files         161      161           
  Lines       10695    10695           
=======================================
  Hits         6645     6645           
  Misses       3414     3414           
  Partials      636      636           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b790d84...947425b. Read the comment docs.

@matthchr
Copy link
Member

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@matthchr
Copy link
Member

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@matthchr matthchr merged commit 92b352a into Azure:master May 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants