Updates for v4

.github/workflows/build-and-stage.yml

@@ -49,7 +49,9 @@ jobs:
           metadata-layer-changed:
             - .github/workflows/build-and-stage.yml
             - Dockerfile-metadata
-            - '/api-*.*'
+            - 'api/**'
+            - 'articles/**'
+            - 'guides/**'
             - build-metadata.sh
             - docfx.json
     - name: Declare image versions

api/v2/configuration/index.md

@@ -20,4 +20,4 @@ Steeltoe adds four additional configuration providers to the preceding list:
 * Placeholder resolvers
 * RandomValue generator
 
-The following sections provide more more detail on each of these new providers.
+The following sections provide more detail on each of these new providers.

api/v3/configuration/index.md

@@ -21,4 +21,4 @@ Steeltoe adds additional configuration providers to the preceding list:
 * RandomValue generator
 * Spring Cloud Config Server
 
-The following sections provide more more detail on each of these new providers.
+The following sections provide more detail on each of these new providers.

api/v3/security/mtls.md

@@ -45,7 +45,7 @@ The above example will create self-signed certificates with an OrgId of `a8fef16
 
 ### Securing Endpoints
 
-In order to use identity certificates for authorization in a service application, services need to be configured and activated and polices need to be applied.
+In order to use identity certificates for authorization in a service application, services need to be configured and activated and policies need to be applied.
 
 #### Adding and using services
 
@@ -76,7 +76,7 @@ public void Configure(IApplicationBuilder app, ...)
 
 >These steps are only required on services that are receiving mTLS-secured requests
 
-#### Applying Authorization Polices
+#### Applying Authorization Policies
 
 Steeltoe includes policies for validating that a request came from an application in the same org or the space. Once you have done the work in the `Startup` class, you can secure endpoints by using the standard ASP.NET Core `Authorize` attribute with one of these security policies.
 

api/v4/bootstrap/index.md

@@ -1,96 +1,85 @@
 # Application Bootstrapping
 
-In order to improve the Steeltoe developer experience, this feature allows the configuration of most Steeltoe components with a single line of code in your application. The package is named [`Steeltoe.Bootstrap.AutoConfiguration`](https://github.com/SteeltoeOSS/Steeltoe/tree/main/src/Bootstrap/src/AutoConfiguration), and it works by applying the same extensions that are already included in Steeltoe packages to automatically wire up each of those components.
+To improve the Steeltoe developer experience, this feature allows the configuration of most Steeltoe components with a single line of code in your application. The package is named [`Steeltoe.Bootstrap.AutoConfiguration`](https://github.com/SteeltoeOSS/Steeltoe/tree/main/src/Bootstrap/src/AutoConfiguration), and it works by calling the same extension methods that are already included in Steeltoe packages to automatically wire up each of those components.
 
-Get started by adding a reference to the AutoConfiguration package (you may want to add other Steeltoe references at this point too, see [the table below](#supported-steeltoe-packages) for the full list of what's supported now):
+Get started by adding a reference to the AutoConfiguration package (you may want to add other Steeltoe references at this point too, see [the table below](#supported-steeltoe-packages) for the full list of what's supported):
 
-```xml
-<ItemGroup>
-    <PackageReference Include="Steeltoe.Bootstrap.AutoConfiguration" Version="4.0.0" />
-</ItemGroup>
+```
+dotnet add package Steeltoe.Bootstrap.AutoConfiguration
 ```
 
- After adding the NuGet reference(s), simply include `.AddSteeltoe()` like you see in this example and you're all set with the basic implementation:
+After adding the NuGet reference(s), simply include `.AddSteeltoe()` like you see in the code below and you're all set with the basic implementation.
 
 ```csharp
-using Microsoft.AspNetCore.Hosting;
-using Microsoft.Extensions.Hosting;
 using Steeltoe.Bootstrap.AutoConfiguration;
 
-namespace WebApplication1
-{
-    public class Program
-    {
-        public static void Main(string[] args)
-        {
-            CreateHostBuilder(args).Build().Run();
-        }
-
-        public static IHostBuilder CreateHostBuilder(string[] args) =>
-            Host.CreateDefaultBuilder(args)
-                .ConfigureWebHostDefaults(webBuilder =>
-                {
-                    webBuilder.UseStartup<Startup>();
-                })
-                .AddSteeltoe();
-    }
-}
-
+var builder = WebApplication.CreateBuilder(args);
+builder.AddSteeltoe();
 ```
 
 ## Supported Steeltoe Packages
 
-`Steeltoe.Bootstrap.AutoConfiguration` is not a meta-package. In order for a Steeltoe feature to be automatically bootstrapped in the application, the appropriate NuGet package must also referenced. The following table describes the Steeltoe package that is required to light up a feature and any additional packages that may also be required:
+`Steeltoe.Bootstrap.AutoConfiguration` is not a meta-package. In order for a Steeltoe feature to be automatically bootstrapped in the application, the appropriate NuGet package must also be referenced. The following table describes the Steeltoe package that is required to light up a feature and any additional packages that may also be installed:
 
-|  Feature Description | Steeltoe Package |Additional Package Required |
+|  Feature Description | Steeltoe Package | Additional Packages |
 | --- | --- | --- |
-| [Config Server Configuration](../configuration/config-server-provider.md) | `Steeltoe.Configuration.ConfigServer` | N/A |
-| [Cloud Foundry Configuration](../configuration/cloud-foundry-provider.md) |`Steeltoe.Configuration.CloudFoundry` |  N/A |
-| [Random Value Provider](../configuration/random-value-provider.md) |`Steeltoe.Configuration.RandomValue` |  N/A |
-| [Placeholder Resolver](../configuration/placeholder-provider.md) |`Steeltoe.Configuration.Placeholder` |  N/A |
-| [Connectors*](../connectors/index.md) |`Steeltoe.Connectors` |  Supported driver (MySQL, PostgreSQL, RabbitMQ, SQL Server, etc) |
-| [Dynamic Serilog](../logging/serilog-logger.md) | `Steeltoe.Logging.DynamicSerilog` | N/A |
-| [Service Discovery](../discovery/index.md) |`Steeltoe.Discovery.Client` | Desired client (Eureka, Consul, Configuration) |
+| [Config Server Configuration Provider](../configuration/config-server-provider.md) | `Steeltoe.Configuration.ConfigServer` | Optional: `Steeltoe.Discovery.Eureka` to use discovery-first |
+| [Cloud Foundry Configuration Provider](../configuration/cloud-foundry-provider.md) |`Steeltoe.Configuration.CloudFoundry` |  N/A |
+| [Random Value Configuration Provider](../configuration/random-value-provider.md) |`Steeltoe.Configuration.RandomValue` |  N/A |
+| [Placeholder Configuration Provider](../configuration/placeholder-provider.md) |`Steeltoe.Configuration.Placeholder` |  N/A |
+| [Encrypted Configuration Provider](../configuration/decryption-provider.md) | `Steeltoe.Configuration.Encryption` | N/A |
+| [Spring Boot Configuration Provider](../configuration/spring-boot-provider.md) | `Steeltoe.Configuration.SpringBoot` | N/A |
+| [Connectors](../connectors/index.md) |`Steeltoe.Connectors` |  Required: Supported driver [^1] (MySQL, PostgreSQL, SQL Server, MongoDB, CosmosDB, Redis, RabbitMQ) |
+| [Eureka Service Discovery](../discovery/netflix-eureka.md) |`Steeltoe.Discovery.Eureka` | Optional: `Steeltoe.Management.Endpoint` for health checks |
+| [Consul Service Discovery](../discovery/hashicorp-consul.md) |`Steeltoe.Discovery.Consul` | N/A |
+| [Configuration-based Service Discovery](../discovery/configuration-based.md) |`Steeltoe.Discovery.Configuration` | N/A |
+| [Dynamic Logging](../logging/dynamic-logging-provider.md) | `Steeltoe.Logging.DynamicLogger` | N/A |
+| [Dynamic Logging with Serilog](../logging/serilog-logger.md) | `Steeltoe.Logging.DynamicSerilog` | N/A |
 | [Actuators](../management/index.md) | `Steeltoe.Management.Endpoint` | N/A |
-| [Distributed Tracing](../tracing/index.md) | `Steeltoe.Management.Tracing` | OpenTelemetry Exporter (Zipkin, Jaeger, OTLP) |
-| [Cloud Foundry Container Identity](../security/mtls.md#configure-settings) | `Steeltoe.Security.Authentication.CloudFoundry` | N/A |
+| [Distributed Tracing](../tracing/index.md) | `Steeltoe.Management.Tracing` | Required: OpenTelemetry Exporter (Zipkin, Jaeger, OTLP) |
 
->\* Individual connector clients will only be configured if a corresponding supported driver NuGet package reference is also included.
+[^1]: Individual connector clients will only be configured if a corresponding supported driver NuGet package reference is also included.
 
 ## Excluding Components
 
-If you wish to exclude a component from the automatic bootstrap process, you may add the feature's assembly name to the exclusions list. One example where this feature would be desired is if you want to control the order configuration providers are added. This example shows how to provide the exclusions list:
+If you wish to exclude a component from the automatic bootstrap process, you may add the feature's assembly name to the exclusions list. One example where this feature would be desired is if you want to control the order in which configuration providers are added. This example shows how to provide exclusions:
 
 ```csharp
-public static IHostBuilder CreateHostBuilder(string[] args)
-{
-    List<string> myExclusions = new () { SteeltoeAssemblyNames.SteeltoeConfigurationConfigServer };
-    return Host.CreateDefaultBuilder(args)
-        .ConfigureWebHostDefaults(webBuilder =>
-        {
-            webBuilder.UseStartup<Startup>();
-        })
-        .AddSteeltoe(myExclusions);
-}
+using Steeltoe.Bootstrap.AutoConfiguration;
+
+HashSet<string> assemblyNamesToExclude = [SteeltoeAssemblyNames.ConfigurationConfigServer];
+builder.AddSteeltoe(assemblyNamesToExclude);
 ```
 
->The static class `SteeltoeAssemblyNames` is `public` so that you can easily find the name of any specific assembly to exclude.
+> [!TIP]
+> The static class `SteeltoeAssemblyNames` enables to easily find the name of any specific assembly to exclude.
 
-## Logging Inside Config Providers
+## Logging inside Configuration Providers
 
 For some Steeltoe components, primarily configuration providers, providing a `LoggerFactory` is required to retrieve logs for debugging. Use the optional parameter to provide one as needed:
 
 ```csharp
-public static IHostBuilder CreateHostBuilder(string[] args)
+using Microsoft.Extensions.Logging.Debug;
+using Steeltoe.Bootstrap.AutoConfiguration;
+
+var loggerFactory = LoggerFactory.Create(loggingBuilder =>
 {
-    LoggerFactory loggerFactory = new (new List<ILoggerProvider> { new DebugLoggerProvider() });
-    return Host.CreateDefaultBuilder(args)
-        .ConfigureWebHostDefaults(webBuilder =>
-        {
-            webBuilder.UseStartup<Startup>();
-        })
-        .AddSteeltoe(loggerFactory: loggerFactory);
-}
+    loggingBuilder.AddDebug(); // or: loggingBuilder.AddConsole();
+    loggingBuilder.SetMinimumLevel(LogLevel.Debug);
+});
+
+builder.AddSteeltoe(loggerFactory);
+```
+
+Alternatively, you can use `BootstrapLoggerFactory`. It logs to the console until the service container has been built.
+Once the service container has become available, it automatically upgrades existing loggers to use the application configuration.
+
+```csharp
+using Steeltoe.Bootstrap.AutoConfiguration;
+using Steeltoe.Common.Logging;
+
+var loggerFactory = BootstrapLoggerFactory.CreateConsole();
+builder.AddSteeltoe(loggerFactory);
 ```
 
 ## Limitations