konsthol/SecDep
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

squash me

Browse Source
This commit is contained in:
konsthol
2023-03-23 01:49:55 +02:00
parent 9c61f013a9
commit f003d3ad57
2 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
assets/pages/azure/Azure_setup.md
View File

@@ -32,10 +32,10 @@ For the Azure Resource Manager the fastest way to get started is by having acces
The values we need translate to the following:
* AZURE_TENANT_ID -> tentantId
* AZURE_SUB_ID -> id from step 3
* AZURE_APP_ID -> appId
* AZURE_PASSWORD -> value of the secret we added
* AZURE_TENANT_ID ➡️ tentantId
* AZURE_SUB_ID ➡️ id from step 3
* AZURE_APP_ID ➡️ appId
* AZURE_PASSWORD ➡️ value of the secret we added
Note: Make sure your subscription is registered to use at least Microsoft.Compute and Microsoft.Network.
From the subscriptions page and resource providers tab.

6
assets/pages/gce/GCE_setup.md
View File

@@ -34,9 +34,9 @@ In as few words as possible, here are the steps to follow:
There are three values needed for authentication with the Google Compute Engine API. The first is the project ID, which is the name of the project you created in the Google Cloud Console. The second is the service account email address, which is the email address of the service account you created in the Google Cloud Console. The third is the path to the JSON file (whose name and path are found by the script's internal logic by providing the private_key_id) that contains the private key for the service account. You can find these values in the JSON file you downloaded from the Google Cloud Console.
Those values are also located in the JSON file and are translate to the following environment variables:
* GCE_PROJECT_ID -> project_id
* GCE_CLIENT_SECRET -> private_key_id
* GCE_CLIENT_ID -> client_email
* GCE_PROJECT_ID ➡️ project_id
* GCE_CLIENT_SECRET ➡️ private_key_id
* GCE_CLIENT_ID ➡️ client_email