Add support for missing resource types

[davidfowl]

https://learn.microsoft.com/en-us/dotnet/aspire/deployment/manifest-format#built-in-resources

• Aspire: Support sqlserver.server.v0, sqlserver.database.v0, sqlserver.connection.v0  #3065
• Aspire: Support rabbitmq.connection.v0, rabbitmq.server.v0 #3060
• Aspire: Support dockerfile.v0 resource #3062

https://learn.microsoft.com/en-us/dotnet/aspire/deployment/manifest-format#azure-specific-resource-types

• Aspire: Support azure.redis.v0 #3061
• Aspire: Support azure.sql.v0, azure.sql.database.v0 #3063
• Aspire: Support azure.appconfiguration.v0 #3064
• Aspire: Support azure.cosmosdb.account.v0, azure.cosmosdb.connection.v0 #3066

[stuartpa]

+1 on getting the SqlServer resource type supported. Currently hitting:

azd init
.
.
Generating files to run your app on Azure:

ERROR: unsupported resource type: sqlserver.server.v1

ASIDE: Is it a bug that the sqlserver.server resource type is v1 (set in WriteSqlServerContainerToManifest() in SqlServerBuilderExtensions.cs). Should it be v0 (like all the others)

[stuartpa]

Is implementing the container resources for items not supported by "az appcontainer add-on create" going to be hard? For example, will azd wait until "az appcontainer add-on sqlserver" support is added before trying to implement sqlserver.server.v1 support.

My understanding is, without appcontainer add-on support for sqlserver, azd will need to do the work to config Ingress, setup a container secret (the mssql equiv to the pg-password), and also pass the required environment variables (e.g. ACCEPT_EULA and MSSQL_SA_PASSWORD).

While sqlserver is not supported by "appcontainer add-ons", will azd still move forward in supporting sqlserver.server.v1 (and do all the wiring up (Ingress/Secret/EnvVars) required in azd), or will azd wait until "az appcontianer add-on" support is added for "sqlserver"?

[vhvb1989]

@stuartpa , azd does not depend on az to provide functionality.

azd interacts with appcontainer service directly, using the sdk clients.

So, no, what az supports or not does not affect azd.

[stuartpa]

Okay, same question rephrased:

While sqlserver is not supported by "appcontainer add-ons", will azd still move forward in supporting sqlserver.server.v1 (and do all the wiring up (Ingress/Secret/EnvVars) required in azd), or will azd wait until "az appcontianer add-on" support is added for "sqlserver"?

[mitchdenny]

We are working through these details at the moment. Our goal is to have it so that when azd sees a sqlserver resource that it will deploy an Azure SQL Database instance.

[davidfowl]

@eerhardt we need to add kafka to this list. ACA's kafka support https://learn.microsoft.com/en-us/azure/container-apps/tutorial-dev-services-kafka?tabs=bash

[eerhardt]

@eerhardt we need to add kafka to this list. ACA's kafka support https://learn.microsoft.com/en-us/azure/container-apps/tutorial-dev-services-kafka?tabs=bash

Note I can't edit the top list, as I'm not a contributor in this repo.

I noticed a couple more missing as well. I've opened the following issues, if you want to add them to this list @ellismg:

• Aspire: Support kafka.server.v0 #3219
• Aspire: Support mongodb.server.v0, mongodb.database.v0 #3220
• Aspire: Support mysql.server.v0, mysql.database.v0 #3221

[javiergardella]

@mitchdenny --> Instead of creating an 'Azure SQL Database instance,' could you set up an entire AKS with two PODs—one for SQL Server and another for the web?

I have already accomplished this, and I can provide the YAML files if needed.

[davidfowl]

@mitchdenny --> Instead of creating an 'Azure SQL Database instance,' could you set up an entire AKS with two PODs—one for SQL Server and another for the web?

There's no support for AKS in aspire via azd for v1. We're primarily targeting ACA. aspirate can deploy SQL containers to Kubernetes.

[MiTschMR]

Also running into the ERROR: generating bicep from manifest: unsupported resource type: sqlserver.server.v1 error/bug. From what I have seen and read, sqlserver.server.v0 is not yet supported, but planned?

Would love to automatically have everything provisioned 😁

[davidfowl]

SQL Server will work in the next preview of azd and aspire.

[rajeshkamal5050]

We will not add hand-crafted, template-based Bicep deployment support in azd. Instead, we will be moving towards using bicep resource type and CDK effort.

• Consider adding a bicep resource type dotnet/aspire#1941
• [Aspire] Support generic bicep resource type #3279