Cosmos DB & Azure Functions differences

[VistianOpenSource]

Are there any documented differences in the way Aspire & Azure functions projects work/interact?

I have a simple solution whereby the Cosmos DB setup occurs correctly within the App Host, and I can get an Api Service solution to correctly reference the Cosmos Db Container, but when I try and repeat the same code within the Azure Functions project, it results in an exception.

The 'nub' of the exception appears to be

Exception: The connection string 'container' does not exist or is missing the container name or database name.

Yet the 'registration within both the host project, the web api project and the azure functions project appears to be identical.

See https://github.com/VistianOpenSource/AspireCosmosDb/tree/master

[VistianOpenSource]

it would appear that there is a difference in functionality with a functions project and other aspire projects. For the functions project it would appear that the connection strings aren't setup in the builder for the functions project but are for others.

The 'workaround' appears to be to create a different connection string in the host, and reference that instead in the functions project.

var refc = builder.AddConnectionString("container2", container.Resource.ConnectionStringExpression);

and then use 'container2' in the functions project. At least the Container instance can now be created.

I'm not sure if this is by design, or an issue.

[davidfowl]

@captainsafia

[chuanboz]

I am curious about this, but I got 404 not found for https://github.com/VistianOpenSource/AspireCosmosDb/tree/master link.

[VistianOpenSource]

Hi, I'd ended up making other changes to this solution that i shouldn't have. This is the public repo https://github.com/VistianOpenSource/AspireCosmosDb-basic

It's awhile since I looked at Aspire & CosmosDb, perhaps this has been addressed?