PublishAsConnectionString

[davidfowl]

Building on top of Parameter support, we can now add PublishAsConnectionString.

var redis = builder.AddRedis("cache").PublishAsConnectionString();

builder.AddProject<Projects.Api>("api");
           .WithReference(redis);

The above will use a container when running but will publish a parameter to the manifest. This is a short cut for the very common scenario:

var redis = builder.ExecutionContext.Operation switch
{
    DistributedApplicationOperation.Run => builder.AddRedis("redis"),
    _ => builder.AddConnectionString("redis")
};

builder.AddProject<Projects.Api>("api");
           .WithReference(redis);

Contributes to #1960

Microsoft Reviewers: Open in CodeFlow

[davidfowl]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[BrennanConroy]

Tests?

[mitchdenny]

There is a wrinkle with this approach. Look at the manifest fragment it generates:

The pg9 resource is a parameter.v0 (good) but that means the value with the connection string is value not connectionString. Which means that when AZD goes to build the database connection string it is probably going to have an issue. We would need the db9 resource to have a connectionString property value that looks like this "{pg9.value};Database=db9"

[mitchdenny]

Actually we could possibly just modify ParameterResource to emit a connectionString when it is used like this.

[davidfowl]

Actually we could possibly just modify ParameterResource to emit a connectionString when it is used like this.

Yes this is what I am thinking too. I originally added this whole surrogate thing, but I think WithReference should just stay the same and we should change how we emit the Parameter to make it work like magic.

[davidfowl]

OK this is ready for another round of review.

[mitchdenny]

One minor tweak suggested. This looks good, but needs to be tested with azd before merge if it hasn't already.

[eerhardt]

Does this need to be public?

[davidfowl]

Yes, other resources might want to expose this. Right now, the other extension method is constrained to ContainerResource, IResourceWithConnectionString

[davidfowl]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).