export TF_VAR_elasticsearch_endpoint="$(az keyvault secret show --vault-name$COMMON_VAULT--id https://$COMMON_VAULT.vault.azure.net/secrets/elastic-endpoint-ado-demo --query value -otsv)"
export TF_VAR_elasticsearch_username="$(az keyvault secret show --vault-name$COMMON_VAULT--id https://$COMMON_VAULT.vault.azure.net/secrets/elastic-username-ado-demo --query value -otsv)"
export TF_VAR_elasticsearch_password="$(az keyvault secret show --vault-name$COMMON_VAULT--id https://$COMMON_VAULT.vault.azure.net/secrets/elastic-password-ado-demo --query value -otsv)"
export TF_VAR_elasticsearch_endpoint="$(az keyvault secret show --vault-name$COMMON_VAULT--id https://$COMMON_VAULT.vault.azure.net/secrets/elastic-endpoint-dp1-demo --query value -otsv)"
export TF_VAR_elasticsearch_username="$(az keyvault secret show --vault-name$COMMON_VAULT--id https://$COMMON_VAULT.vault.azure.net/secrets/elastic-username-dp1-demo --query value -otsv)"
export TF_VAR_elasticsearch_password="$(az keyvault secret show --vault-name$COMMON_VAULT--id https://$COMMON_VAULT.vault.azure.net/secrets/elastic-password-dp1-demo --query value -otsv)"
EOF
cp .envrc_${UNIQUE} .envrc
cp.envrc .envrc_${UNIQUE}
```
## Configure Key Access in Manifest Repository
The public key of the [RSA key pair](#create-an-rsa-key-pair-for-a-deploy-key-for-the-flux-repository) previously created needs to be added as a deploy key. Note: _If you do not own the repository, you will have to fork it before proceeding_.
Use the contents of the Secret as shown above.
The public key of the `azure-aks-gitops-ssh-key` previously created needs to be added as a deploy key in your Azure DevOPS Project, follow these [steps](https://docs.microsoft.com/en-us/azure/devops/repos/git/use-ssh-keys-to-authenticate?view=azure-devops&tabs=current-page#step-2--add-the-public-key-to-azure-devops-servicestfs) to add your public SSH key to your ADO environment.
Next, in your Azure DevOPS Project, follow these [steps](https://docs.microsoft.com/en-us/azure/devops/repos/git/use-ssh-keys-to-authenticate?view=azure-devops&tabs=current-page#step-2--add-the-public-key-to-azure-devops-servicestfs) to add your public SSH key to your ADO environment.
> This typically takes about 30 minutes to complete.
> This typically takes about 10 minutes to complete.
__Create Empty Repositories__
...
...
@@ -54,7 +54,12 @@ Variable Group Name: `Mirror Variables`
| ACCESS_TOKEN | <your_personal_access_token> |
Manually create a Personal Access Token following the [documentation](https://docs.microsoft.com/en-us/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate?view=azure-devops&tabs=preview-page) and add a Variable called `ACCESS_TOKEN` with the value being the PAT created.
```bash
ACCESS_TOKEN=<your_access_token>
az pipelines variable-group create \
--name"Mirror Variables"\
--authorizetrue\
...
...
@@ -70,17 +75,21 @@ az pipelines variable-group create \
Manually create a Personal Access Token following the [documentation](https://docs.microsoft.com/en-us/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate?view=azure-devops&tabs=preview-page) and add a Variable called `ACCESS_TOKEN` with the value being the PAT created.
__Create Mirror Pipeline__
Clone the Project Repository `osdu-mvp`, and add the pipeline.
__Create Pipeline__
Manually Create a Pipeline [`gitlab-sync`](../devops/gitlab-sync.yml)