Skip to content

Commit

Permalink
Update deployment steps for drone scheduler (#125)
Browse files Browse the repository at this point in the history 
The deployment steps try to get the Resource ID and Client ID from the "azuredeploy" deployment but these are actually returned in the "azuredeploy-identities" deployment
  • Loading branch information
Mike Wasson authored and Fernando Antivero committed Apr 15, 2019
1 parent 10c3d27 commit 26e5bde
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions deployment.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -391,8 +391,8 @@ Create and set up pod identity

```bash
# Extract outputs from deployment
export DRONESCHEDULER_PRINCIPAL_RESOURCE_ID=$(az group deployment show -g $RESOURCE_GROUP -n azuredeploy --query properties.outputs.droneSchedulerPrincipalResourceId.value -o tsv) && \
export DRONESCHEDULER_PRINCIPAL_CLIENT_ID=$(az group deployment show -g $RESOURCE_GROUP -n azuredeploy --query properties.outputs.droneSchedulerPrincipalClientId.value -o tsv)
export DRONESCHEDULER_PRINCIPAL_RESOURCE_ID=$(az group deployment show -g $RESOURCE_GROUP -n azuredeploy-identities --query properties.outputs.droneSchedulerPrincipalResourceId.value -o tsv) && \
export DRONESCHEDULER_PRINCIPAL_CLIENT_ID=$(az group deployment show -g $RESOURCE_GROUP -n azuredeploy-identities --query properties.outputs.droneSchedulerPrincipalClientId.value -o tsv)
```

Build and publish the container image
Expand Down

0 comments on commit 26e5bde

Please sign in to comment.