Azure Pipelines Cosmos DB emulator task: endpoint variable is unset
Lauri Lehman
6
Reputation points
According to the documentation, the Azure Pipelines Cosmos DB Emulator tasks exports a pipeline variable $(CosmosDbEmulator.Endpoint). However, in reality the variable is not set. To reproduce this, create an emulator task and try to print the variable:
steps:
- task: azure-cosmosdb.emulator-public-preview.run-cosmosdbemulatorcontainer.CosmosDbEmulator@2
name: runCosmosDbTask
- script: echo Cosmos DB endpoint is $(CosmosDbEmulator.Endpoint)
The output is:
Cosmos DB endpoint is $(CosmosDbEmulator.Endpoint)
As you see, the expression is printed explicitly, which is a sign that the variable is not set. The Cosmos DB Emulator task is running fine, and the endpoint address can be seen from the task output:
Name Value
---- -----
GremlinEndpoint http://75d6f74e847d:8901/
TableEndpoint http://75d6f74e847d:8902/
Ports {10251, 10252, 8081, 10350...}
MongoDBEndpoint mongodb://75d6f74e847d:10255/
ContainerName /azure-cosmosdb-emulator
HostDirectory D:\a\1\b\azure-cosmosdb-emulator
ContainerId 75d6f74e847d8c767fa99062dfaa80e9669d027045ddd5afc4054691e2f3ad51
CassandraEndpoint tcp://75d6f74e847d:10350/
IPAddress 172.28.47.159
Endpoint https://75d6f74e847d:8081/
Azure Cosmos DB
Azure Cosmos DB
An Azure NoSQL database service for app development.
1,906 questions
Sign in to answer