diff --git a/docs/docs/v2/connectors/gemfire.md b/docs/docs/v2/connectors/gemfire.md index 65fa9078..d18c69f2 100644 --- a/docs/docs/v2/connectors/gemfire.md +++ b/docs/docs/v2/connectors/gemfire.md @@ -67,7 +67,7 @@ cf bind-service myApp myPCCService cf restage myApp ``` -If your application fails to [programmatically create regions](https://techdocs.broadcom.com/us/en/vmware-tanzu/data-solutions/tanzu-gemfire-native-client/10-4/gf-nc/dotnet-geode-native-docs-dotnet-regions-regions.html), use the [gfsh CLI](https://techdocs.broadcom.com/us/en/vmware-tanzu/data-solutions/tanzu-gemfire/10-1/gf/tools_modules-gfsh-chapter_overview.html) to create it. You will need the gfsh url and the cluster operator credentials provided in the service binding: +If your application fails to [programmatically create regions](https://techdocs.broadcom.com/us/en/vmware-tanzu/data-solutions/tanzu-gemfire-native-client/10-4/gf-nc/dotnet-geode-native-docs-dotnet-regions-regions.html), use the [gfsh CLI](https://techdocs.broadcom.com/us/en/vmware-tanzu/data-solutions/tanzu-gemfire/10-3/gf/tools_modules-gfsh-chapter_overview.html) to create it. You will need the gfsh url and the cluster operator credentials provided in the service binding: ```json "p-cloudcache": [{ diff --git a/docs/docs/v2/connectors/mysql.md b/docs/docs/v2/connectors/mysql.md index 0a71ac1b..daa2b480 100644 --- a/docs/docs/v2/connectors/mysql.md +++ b/docs/docs/v2/connectors/mysql.md @@ -101,7 +101,7 @@ cf bind-service myApp myMySqlService cf restage myApp ``` ->NOTE: The preceding commands assume you use [Tanzu for MySQL](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/tanzu-mysql-tanzu-platform/10-1/mysql-tp/index.html), provided by Tanzu Platform. If you use a different service, you must adjust the `create-service` command to fit your environment. +>NOTE: The preceding commands assume you use [Tanzu for MySQL](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/tanzu-mysql-tanzu-platform/11-0/mysql-tp/index.html), provided by Tanzu Platform. If you use a different service, you must adjust the `create-service` command to fit your environment. Version 2.1.1+ of this connector works with the [Open Service Broker for Azure](https://github.com/Azure/open-service-broker-azure) (archived). Be sure to set `mysql:client:urlEncodedCredentials` to `true` as this broker may provide credentials that have been URL Encoded. diff --git a/docs/docs/v2/fileshares/index.md b/docs/docs/v2/fileshares/index.md index 48b00e9b..940a60d6 100644 --- a/docs/docs/v2/fileshares/index.md +++ b/docs/docs/v2/fileshares/index.md @@ -2,4 +2,4 @@ Steeltoe's `WindowsNetworkFileShare` provides a simplified experience for interacting with SMB file shares by making [P/Invoke calls](https://learn.microsoft.com/cpp/dotnet/how-to-call-native-dlls-from-managed-code-using-pinvoke) to underlying Windows APIs, specifically to `mpr.dll`. For more background on SMB, see [Microsoft's SMB documentation](https://learn.microsoft.com/windows/win32/fileio/microsoft-smb-protocol-and-cifs-protocol-overview) -Network shares are not the most cloud-native way to deal with files. For new development consider exploring message queues, caches, blob stores, and/or NoSQL stores. The alternatives offer greater resiliency and decoupling from backing services. With that said, sometimes the alternatives aren't viable. We're not here to judge you. For .NET applications deployed to Microsoft Windows Servers, Steeltoe provides a stepping stone towards cloud-native in the form of the `WindowsNetworkFileShare`. For applications deployed to Linux hosts on TAS, [volume services](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/elastic-application-runtime/10-3/eart/services-using-vol-services.html) is available. +Network shares are not the most cloud-native way to deal with files. For new development consider exploring message queues, caches, blob stores, and/or NoSQL stores. The alternatives offer greater resiliency and decoupling from backing services. With that said, sometimes the alternatives aren't viable. We're not here to judge you. For .NET applications deployed to Microsoft Windows Servers, Steeltoe provides a stepping stone towards cloud-native in the form of the `WindowsNetworkFileShare`. For applications deployed to Linux hosts on TAS, [volume services](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/elastic-application-runtime/11-0/eart/services-using-vol-services.html) is available. diff --git a/docs/docs/v2/logging/dynamic-logging-provider.md b/docs/docs/v2/logging/dynamic-logging-provider.md index d6ddd4cb..355cf7c2 100644 --- a/docs/docs/v2/logging/dynamic-logging-provider.md +++ b/docs/docs/v2/logging/dynamic-logging-provider.md @@ -2,7 +2,7 @@ This logging provider is a wrapper around the [Microsoft Console Logging](https://github.com/aspnet/Logging) provider. This wrapper allows for querying the currently defined loggers and their levels as well as then modifying the levels dynamically at runtime. -For more information on how to use [Apps Manager](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/elastic-application-runtime/10-3/eart/dev-console.html) on Cloud Foundry for viewing and modifying logging levels, see the Using Actuators with Apps Manager section of the Tanzu Platform documentation. +For more information on how to use [Apps Manager](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/elastic-application-runtime/11-0/eart/dev-console.html) on Cloud Foundry for viewing and modifying logging levels, see the Using Actuators with Apps Manager section of the Tanzu Platform documentation. > NOTE: The Apps Manager integration involves sending the fully-qualified logger name over HTTP. Avoid using colons in the name of a logger to prevent invalid HTTP Requests. diff --git a/docs/docs/v2/logging/index.md b/docs/docs/v2/logging/index.md index a6fd74a2..4157f2c8 100644 --- a/docs/docs/v2/logging/index.md +++ b/docs/docs/v2/logging/index.md @@ -2,4 +2,4 @@ Steeltoe adds a Logging provider to the set of available logging packages in order to support the Steeltoe Management Logger endpoint. -When used with the Steeltoe Logger Management endpoint, this package enables dynamically changing the logging levels for running applications with the [Apps Manager](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/elastic-application-runtime/10-3/eart/dev-console.html) on Cloud Foundry. +When used with the Steeltoe Logger Management endpoint, this package enables dynamically changing the logging levels for running applications with the [Apps Manager](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/elastic-application-runtime/11-0/eart/dev-console.html) on Cloud Foundry. diff --git a/docs/docs/v2/management/dump.md b/docs/docs/v2/management/dump.md index 9c51b5c9..5f2e5ecb 100644 --- a/docs/docs/v2/management/dump.md +++ b/docs/docs/v2/management/dump.md @@ -2,7 +2,7 @@ The Steeltoe thread dump endpoint can be used to generate a snapshot of information about all the threads in your application. That snapshot includes several bits of information for each thread, including the thread's state, a stack trace, any monitor locks held by the thread, any monitor locks the thread is waiting on, and other details. ->NOTE: At this time, thread dumps are only possible on the Windows operating system. When integrating with the [Apps Manager](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/elastic-application-runtime/10-3/eart/dev-console.html), you will not have the ability to obtain thread dumps from apps running on Linux cells. +>NOTE: At this time, thread dumps are only possible on the Windows operating system. When integrating with the [Apps Manager](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/elastic-application-runtime/11-0/eart/dev-console.html), you will not have the ability to obtain thread dumps from apps running on Linux cells. ## Configure Settings diff --git a/docs/docs/v2/management/heapdump.md b/docs/docs/v2/management/heapdump.md index 94ac860c..d9bd94e5 100644 --- a/docs/docs/v2/management/heapdump.md +++ b/docs/docs/v2/management/heapdump.md @@ -2,7 +2,7 @@ The Steeltoe heap dump endpoint can be used to generate and download a mini-dump of your application. The mini-dump can then be read into Visual Studio for analysis. ->NOTE: At this time, dumps are only possible on the Windows operating system. When integrating with the [Apps Manager](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/elastic-application-runtime/10-3/eart/dev-console.html), you will not have the ability to obtain dumps from apps running on Linux cells. For older versions of Apps Manager, there was a bug where the heap dump filename ends with the `.hprof` extension instead of the usual `.dmp` extension. This may cause problems when opening the dump with Visual Studio or some other diagnostic tool. As a workaround, you can rename the file to use the `.dmp` extension. Furthermore, heap dumps from Steeltoe are always gzipped and are expected to be returned with a `.gz` on the end. If the file you receive does not include `.gz`, you should manually change the extension to `.dmp.gz` and unzip the file before attempting to open it, or else you are likely to receive a compatibility error. +>NOTE: At this time, dumps are only possible on the Windows operating system. When integrating with the [Apps Manager](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/elastic-application-runtime/11-0/eart/dev-console.html), you will not have the ability to obtain dumps from apps running on Linux cells. For older versions of Apps Manager, there was a bug where the heap dump filename ends with the `.hprof` extension instead of the usual `.dmp` extension. This may cause problems when opening the dump with Visual Studio or some other diagnostic tool. As a workaround, you can rename the file to use the `.dmp` extension. Furthermore, heap dumps from Steeltoe are always gzipped and are expected to be returned with a `.gz` on the end. If the file you receive does not include `.gz`, you should manually change the extension to `.dmp.gz` and unzip the file before attempting to open it, or else you are likely to receive a compatibility error. ## Configure Settings diff --git a/docs/docs/v2/management/metrics.md b/docs/docs/v2/management/metrics.md index d4cba739..3ff43a94 100644 --- a/docs/docs/v2/management/metrics.md +++ b/docs/docs/v2/management/metrics.md @@ -83,7 +83,7 @@ dotnet add package Steeltoe.Management.ExporterCore --version 2.* The Metrics Forwarder for TAS (discontinued) is a service that allows apps to emit metrics to the [Loggregator](https://docs.cloudfoundry.org/loggregator/architecture.html) system and consume those metrics from the [Loggregator Firehose](https://docs.cloudfoundry.org/loggregator/architecture.html#-loggregator-firehose-architecture). -You can interact with the service through the Cloud Foundry Command Line Interface (cf CLI), [Apps Manager](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/elastic-application-runtime/10-3/eart/dev-console.html), and an HTTP API. See the Tanzu Platform documentation for details on how to use the service in your application. +You can interact with the service through the Cloud Foundry Command Line Interface (cf CLI), [Apps Manager](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/elastic-application-runtime/11-0/eart/dev-console.html), and an HTTP API. See the Tanzu Platform documentation for details on how to use the service in your application. Metrics Forwarder for TAS (discontinued) enables users to do the following: diff --git a/docs/docs/v2/management/prometheus.md b/docs/docs/v2/management/prometheus.md index cc02202b..8da7e1c5 100644 --- a/docs/docs/v2/management/prometheus.md +++ b/docs/docs/v2/management/prometheus.md @@ -49,7 +49,7 @@ dotnet add package Steeltoe.Management.EndpointCore --version 2.* ## Cloud Foundry Forwarder -The Metrics Forwarder for TAS is no longer supported on Tanzu Application Service (TAS) v2.5 and later. To emit custom metrics on PAS v2.5 or later, use the [Metric Registrar](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/elastic-application-runtime/10-3/eart/metric-registrar-index.html) to emit metrics to [Loggregator](https://docs.cloudfoundry.org/loggregator/architecture.html). +The Metrics Forwarder for TAS is no longer supported on Tanzu Application Service (TAS) v2.5 and later. To emit custom metrics on PAS v2.5 or later, use the [Metric Registrar](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/elastic-application-runtime/11-0/eart/metric-registrar-index.html) to emit metrics to [Loggregator](https://docs.cloudfoundry.org/loggregator/architecture.html). To register your endpoint for metrics collection install the metrics-registrar plugin and use it to register your endpoint. diff --git a/docs/docs/v2/management/using-endpoints.md b/docs/docs/v2/management/using-endpoints.md index 3c1ae595..c43b9c68 100644 --- a/docs/docs/v2/management/using-endpoints.md +++ b/docs/docs/v2/management/using-endpoints.md @@ -35,7 +35,7 @@ The following table describes the available Steeltoe management endpoints that c Each endpoint has an associated ID. When you want to expose that endpoint over HTTP, that ID is used in the mapped URL that exposes the endpoint. For example, the `health` endpoint below is mapped to `/health`. ->NOTE: When you want to integrate with the [Apps Manager](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/elastic-application-runtime/10-3/eart/dev-console.html), you need to configure the global management path prefix to be `/cloudfoundryapplication`. To do so, add `management:endpoints:path=/cloudfoundryapplication` to your configuration. +>NOTE: When you want to integrate with the [Apps Manager](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/elastic-application-runtime/11-0/eart/dev-console.html), you need to configure the global management path prefix to be `/cloudfoundryapplication`. To do so, add `management:endpoints:path=/cloudfoundryapplication` to your configuration. ## Add NuGet References diff --git a/docs/docs/v2/security/credhub-api-client.md b/docs/docs/v2/security/credhub-api-client.md index d4b6ff8d..b7cf10e6 100644 --- a/docs/docs/v2/security/credhub-api-client.md +++ b/docs/docs/v2/security/credhub-api-client.md @@ -1,6 +1,6 @@ # CredHub API Client -[CredHub](https://github.com/cloudfoundry/credhub) manages credentials such as passwords, certificates, certificate authorities, ssh keys, rsa keys, and other arbitrary values. Steeltoe provides the `CredHubBase` library for interacting with the [CredHub API](https://docs.cloudfoundry.org/api/credhub/version/main/) and provides the `CredHubCore` library for making that client library simpler to use in ASP.NET Core applications. Cloud Foundry is not required for the CredHub server or client but is used in this documentation as the hosting environment. You may wish to review the documentation for [CredHub on Tanzu Platform](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/elastic-application-runtime/10-3/eart/credhub-index.html). If you do not already have a UAA user to use for this test, you will need to use the UAA command line tool to establish some security credentials for the sample app. Choose one of the provided `credhub-setup` scripts in the folder `samples/Security/scripts` to target your Cloud Foundry environment and create a UAA client with permissions to read and write in CredHub. +[CredHub](https://github.com/cloudfoundry/credhub) manages credentials such as passwords, certificates, certificate authorities, ssh keys, rsa keys, and other arbitrary values. Steeltoe provides the `CredHubBase` library for interacting with the [CredHub API](https://docs.cloudfoundry.org/api/credhub/version/main/) and provides the `CredHubCore` library for making that client library simpler to use in ASP.NET Core applications. Cloud Foundry is not required for the CredHub server or client but is used in this documentation as the hosting environment. You may wish to review the documentation for [CredHub on Tanzu Platform](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/elastic-application-runtime/11-0/eart/credhub-index.html). If you do not already have a UAA user to use for this test, you will need to use the UAA command line tool to establish some security credentials for the sample app. Choose one of the provided `credhub-setup` scripts in the folder `samples/Security/scripts` to target your Cloud Foundry environment and create a UAA client with permissions to read and write in CredHub. >NOTE: If you choose to change the values for `UAA_CLIENT_ID` or `UAA_CLIENT_SECRET`, be sure to update the credentials in appsettings.json diff --git a/docs/docs/v3/connectors/mysql.md b/docs/docs/v3/connectors/mysql.md index 13245b24..48cbdcd5 100644 --- a/docs/docs/v3/connectors/mysql.md +++ b/docs/docs/v3/connectors/mysql.md @@ -98,7 +98,7 @@ cf bind-service myApp myMySqlService cf restage myApp ``` ->The preceding commands assume you use [Tanzu for MySQL](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/tanzu-mysql-tanzu-platform/10-1/mysql-tp/index.html), provided by Tanzu Platform. If you use a different service, you must adjust the `create-service` command to fit your environment. +>The preceding commands assume you use [Tanzu for MySQL](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/tanzu-mysql-tanzu-platform/11-0/mysql-tp/index.html), provided by Tanzu Platform. If you use a different service, you must adjust the `create-service` command to fit your environment. This connector also works with the [Open Service Broker for Azure](https://github.com/Azure/open-service-broker-azure) (archived). diff --git a/docs/docs/v3/fileshares/index.md b/docs/docs/v3/fileshares/index.md index e97b14f7..52d8d6da 100644 --- a/docs/docs/v3/fileshares/index.md +++ b/docs/docs/v3/fileshares/index.md @@ -2,4 +2,4 @@ Steeltoe's `WindowsNetworkFileShare` provides a simplified experience for interacting with SMB file shares by making [P/Invoke calls](https://learn.microsoft.com/cpp/dotnet/how-to-call-native-dlls-from-managed-code-using-pinvoke) to underlying Windows APIs, specifically to `mpr.dll`. For more background on SMB, see [Microsoft's SMB documentation](https://learn.microsoft.com/windows/win32/fileio/microsoft-smb-protocol-and-cifs-protocol-overview) -Network shares are not the most cloud-native way to deal with files. For new development, consider exploring message queues, caches, blob stores, and NoSQL stores. The alternatives offer greater resiliency and decoupling from backing services. That said, sometimes the alternatives are not viable. For .NET applications deployed to Microsoft Windows Servers, Steeltoe provides a stepping stone towards cloud-native in the form of the `WindowsNetworkFileShare`. For applications deployed to Linux hosts on TAS, [volume services](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/elastic-application-runtime/10-3/eart/services-using-vol-services.html) are available. +Network shares are not the most cloud-native way to deal with files. For new development, consider exploring message queues, caches, blob stores, and NoSQL stores. The alternatives offer greater resiliency and decoupling from backing services. That said, sometimes the alternatives are not viable. For .NET applications deployed to Microsoft Windows Servers, Steeltoe provides a stepping stone towards cloud-native in the form of the `WindowsNetworkFileShare`. For applications deployed to Linux hosts on TAS, [volume services](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/elastic-application-runtime/11-0/eart/services-using-vol-services.html) are available. diff --git a/docs/docs/v3/management/metrics.md b/docs/docs/v3/management/metrics.md index b9d34b29..e3deb2ce 100644 --- a/docs/docs/v3/management/metrics.md +++ b/docs/docs/v3/management/metrics.md @@ -103,7 +103,7 @@ In addition, the following settings can be used to set the application and servi ### Tanzu Application Service (TAS for VMs) -To emit custom metrics on TAS for VMs v2.5 or later, use the [Metric Registrar](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/elastic-application-runtime/10-3/eart/metric-registrar-index.html) to emit metrics to [Loggregator](https://docs.cloudfoundry.org/loggregator/architecture.html). +To emit custom metrics on TAS for VMs v2.5 or later, use the [Metric Registrar](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/elastic-application-runtime/11-0/eart/metric-registrar-index.html) to emit metrics to [Loggregator](https://docs.cloudfoundry.org/loggregator/architecture.html). To register your endpoint for metrics collection, install the metrics-registrar plugin and use it to register your endpoint: diff --git a/docs/docs/v3/management/threaddump.md b/docs/docs/v3/management/threaddump.md index 0446d201..a105f632 100644 --- a/docs/docs/v3/management/threaddump.md +++ b/docs/docs/v3/management/threaddump.md @@ -2,7 +2,7 @@ The Steeltoe thread dump endpoint can be used to generate a snapshot of information about all the threads in your application. That snapshot includes several bits of information for each thread, including the thread's state, a stack trace, any monitor locks held by the thread, any monitor locks the thread is waiting on, and other details. ->NOTE: At this time, thread dumps are only possible on the Windows operating system. When integrating with the [Apps Manager](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/elastic-application-runtime/10-3/eart/dev-console.html), you will not have the ability to obtain thread dumps from apps running on Linux cells. +>NOTE: At this time, thread dumps are only possible on the Windows operating system. When integrating with the [Apps Manager](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/elastic-application-runtime/11-0/eart/dev-console.html), you will not have the ability to obtain thread dumps from apps running on Linux cells. ## Configure Settings diff --git a/docs/docs/v3/security/credhub-api-client.md b/docs/docs/v3/security/credhub-api-client.md index c0285a7e..60136ecc 100644 --- a/docs/docs/v3/security/credhub-api-client.md +++ b/docs/docs/v3/security/credhub-api-client.md @@ -1,6 +1,6 @@ # CredHub API Client -[CredHub](https://github.com/cloudfoundry/credhub) manages credentials, such as passwords, certificates, certificate authorities, ssh keys, RSA keys, and other arbitrary values. Steeltoe provides the `CredHubBase` library for interacting with the [CredHub API](https://docs.cloudfoundry.org/api/credhub/version/main/) and provides the `CredHubCore` library for making that client library simpler to use in ASP.NET Core applications. Cloud Foundry is not required for the CredHub server or client but is used in this documentation as the hosting environment. You may wish to review the documentation for [CredHub on Tanzu Platform](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/elastic-application-runtime/10-3/eart/credhub-index.html). If you do not already have a UAA user to use for this test, you need to use the UAA command-line tool to establish some security credentials for the sample application. Choose one of the provided `credhub-setup` scripts in the folder `samples/Security/scripts` to target your Cloud Foundry environment and create a UAA client with permissions to read and write in CredHub. +[CredHub](https://github.com/cloudfoundry/credhub) manages credentials, such as passwords, certificates, certificate authorities, ssh keys, RSA keys, and other arbitrary values. Steeltoe provides the `CredHubBase` library for interacting with the [CredHub API](https://docs.cloudfoundry.org/api/credhub/version/main/) and provides the `CredHubCore` library for making that client library simpler to use in ASP.NET Core applications. Cloud Foundry is not required for the CredHub server or client but is used in this documentation as the hosting environment. You may wish to review the documentation for [CredHub on Tanzu Platform](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/elastic-application-runtime/11-0/eart/credhub-index.html). If you do not already have a UAA user to use for this test, you need to use the UAA command-line tool to establish some security credentials for the sample application. Choose one of the provided `credhub-setup` scripts in the folder `samples/Security/scripts` to target your Cloud Foundry environment and create a UAA client with permissions to read and write in CredHub. >If you choose to change the values for `UAA_CLIENT_ID` or `UAA_CLIENT_SECRET`, be sure to update the credentials in `appsettings.json`. diff --git a/docs/docs/v4/connectors/extensibility.md b/docs/docs/v4/connectors/extensibility.md index ac19dcd6..e43bf424 100644 --- a/docs/docs/v4/connectors/extensibility.md +++ b/docs/docs/v4/connectors/extensibility.md @@ -3,7 +3,7 @@ Steeltoe Connectors cover a fixed set of supported data stores and messaging systems (PostgreSQL, MySQL, SQL Server, MongoDB, Cosmos DB, RabbitMQ, and Redis/Valkey). They are not open-ended plug-ins; extensibility means shaping platform credentials into the connection strings external drivers for those built-in connectors already understand. -Connectors map credentials from [Cloud Foundry service bindings](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/elastic-application-runtime/10-3/eart/binding-credentials.html) and +Connectors map credentials from [Cloud Foundry service bindings](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/elastic-application-runtime/11-0/eart/binding-credentials.html) and [Service Binding Spec for Kubernetes](https://github.com/servicebinding/spec#well-known-secret-entries) into configuration keys starting with `steeltoe:service-bindings` and merge them with local settings from `Steeltoe:Client`. Each connector runs the binding logic for its own service type. diff --git a/docs/docs/v4/connectors/mysql.md b/docs/docs/v4/connectors/mysql.md index 8ea38338..306dd6f6 100644 --- a/docs/docs/v4/connectors/mysql.md +++ b/docs/docs/v4/connectors/mysql.md @@ -153,7 +153,7 @@ A complete sample app that uses Entity Framework Core with MySQL is provided at This Connector supports the following service brokers: -- [Tanzu for MySQL on Tanzu Platform](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/tanzu-mysql-tanzu-platform/10-1/mysql-tp/index.html) +- [Tanzu for MySQL on Tanzu Platform](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/tanzu-mysql-tanzu-platform/11-0/mysql-tp/index.html) - [Tanzu Cloud Service Broker for GCP](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/cloud-service-broker-gcp/1-8/csb-gcp/reference-gcp-mysql.html) - [Tanzu Cloud Service Broker for AWS](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/cloud-service-broker-aws/1-15/csb-aws/reference-aws-mysql.html) diff --git a/docs/docs/v4/connectors/postgresql.md b/docs/docs/v4/connectors/postgresql.md index c9fd7bf5..925fd2fc 100644 --- a/docs/docs/v4/connectors/postgresql.md +++ b/docs/docs/v4/connectors/postgresql.md @@ -147,7 +147,7 @@ A complete sample app that uses Entity Framework Core with PostgreSQL is provide This Connector supports the following service brokers: -- [Tanzu for Postgres on Tanzu Platform](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/tanzu-postgres-tanzu-platform/10-2/postgres-tp/index.html) +- [Tanzu for Postgres on Tanzu Platform](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/tanzu-postgres-tanzu-platform/11-0/postgres-tp/index.html) - [Tanzu Cloud Service Broker for GCP](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/cloud-service-broker-gcp/1-8/csb-gcp/reference-gcp-postgresql.html) - [Tanzu Cloud Service Broker for AWS](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/cloud-service-broker-aws/1-15/csb-aws/reference-aws-postgres.html) diff --git a/docs/docs/v4/connectors/rabbitmq.md b/docs/docs/v4/connectors/rabbitmq.md index 1712c3bd..301a3938 100644 --- a/docs/docs/v4/connectors/rabbitmq.md +++ b/docs/docs/v4/connectors/rabbitmq.md @@ -89,7 +89,7 @@ A complete sample app that uses `IConnection` is provided at https://github.com/ This Connector supports the following service brokers: -- [Tanzu RabbitMQ on Cloud Foundry](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/tanzu-rabbitmq-tanzu-platform/10-0/rabbitmq-tp/index.html) +- [Tanzu RabbitMQ on Cloud Foundry](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/tanzu-rabbitmq-tanzu-platform/11-0/rabbitmq-tp/index.html) You can create and bind an instance to your application by using the Cloud Foundry CLI. diff --git a/docs/docs/v4/connectors/redis.md b/docs/docs/v4/connectors/redis.md index 2cff4bb8..4583e731 100644 --- a/docs/docs/v4/connectors/redis.md +++ b/docs/docs/v4/connectors/redis.md @@ -117,7 +117,7 @@ For a complete sample app that uses `IDistributedCache`, see https://github.com/ This Connector supports the following service brokers: -- [Tanzu for Valkey on Tanzu Platform](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/tanzu-valkey-tanzu-platform/10-2/valkey-tp/index.html) +- [Tanzu for Valkey on Tanzu Platform](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/tanzu-valkey-tanzu-platform/11-0/valkey-tp/index.html) - [Tanzu Cloud Service Broker for Microsoft Azure](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/cloud-service-broker-azure/1-13/csb-azure/reference-azure-redis.html) - [Tanzu Cloud Service Broker for AWS](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/cloud-service-broker-aws/1-15/csb-aws/reference-aws-redis.html) diff --git a/docs/docs/v4/fileshares/index.md b/docs/docs/v4/fileshares/index.md index 2abf91d6..1896dbd7 100644 --- a/docs/docs/v4/fileshares/index.md +++ b/docs/docs/v4/fileshares/index.md @@ -2,4 +2,4 @@ The Steeltoe `WindowsNetworkFileShare` class provides a simplified experience for interacting with SMB file shares by making [P/Invoke calls](https://learn.microsoft.com/cpp/dotnet/how-to-call-native-dlls-from-managed-code-using-pinvoke) to underlying Windows APIs, specifically to `mpr.dll`. For more information about SMB, see the [Microsoft SMB Protocol documentation](https://learn.microsoft.com/windows/win32/fileio/microsoft-smb-protocol-and-cifs-protocol-overview). -Network shares are not the most cloud-native way to deal with files. For new development, consider exploring message queues, caches, blob stores, and NoSQL stores. The alternatives offer greater resiliency and decoupling from backing services. That said, sometimes the alternatives are not viable. For .NET applications deployed to Microsoft Windows Servers, Steeltoe provides a stepping stone towards cloud-native deployment in the form of the `WindowsNetworkFileShare`. For applications deployed to Linux hosts on the Tanzu Platform, [volume services](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/elastic-application-runtime/10-3/eart/services-using-vol-services.html) are available. +Network shares are not the most cloud-native way to deal with files. For new development, consider exploring message queues, caches, blob stores, and NoSQL stores. The alternatives offer greater resiliency and decoupling from backing services. That said, sometimes the alternatives are not viable. For .NET applications deployed to Microsoft Windows Servers, Steeltoe provides a stepping stone towards cloud-native deployment in the form of the `WindowsNetworkFileShare`. For applications deployed to Linux hosts on the Tanzu Platform, [volume services](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/elastic-application-runtime/11-0/eart/services-using-vol-services.html) are available. diff --git a/docs/docs/v4/management/cloud-foundry.md b/docs/docs/v4/management/cloud-foundry.md index 9a5da7e0..958cdbdb 100644 --- a/docs/docs/v4/management/cloud-foundry.md +++ b/docs/docs/v4/management/cloud-foundry.md @@ -1,6 +1,6 @@ # Cloud Foundry Integration -Integration with [Tanzu Apps Manager](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/elastic-application-runtime/10-3/eart/dev-console.html) is accomplished by adding the Cloud Foundry management endpoint to your application. +Integration with [Tanzu Apps Manager](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/elastic-application-runtime/11-0/eart/dev-console.html) is accomplished by adding the Cloud Foundry management endpoint to your application. When used, this endpoint enables the following additional functionality on Cloud Foundry: diff --git a/docs/docs/v4/management/loggers.md b/docs/docs/v4/management/loggers.md index d81a64a9..ca0330bd 100644 --- a/docs/docs/v4/management/loggers.md +++ b/docs/docs/v4/management/loggers.md @@ -121,7 +121,7 @@ For example, changing the minimum log level of `Microsoft.AspNetCore` affects al `Microsoft.AspNetCore`; for example, `Microsoft.AspNetCore` and `Microsoft.AspNetCore.Cors` (but not `Microsoft.AspNetCoreExtra`). > [!NOTE] -> [Spring Boot Admin](https://www.baeldung.com/spring-boot-changing-log-level-at-runtime) and [Tanzu Apps Manager](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/elastic-application-runtime/10-3/eart/dev-console.html) +> [Spring Boot Admin](https://www.baeldung.com/spring-boot-changing-log-level-at-runtime) and [Tanzu Apps Manager](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/elastic-application-runtime/11-0/eart/dev-console.html) > provide a UI to change the minimum levels at runtime. For compatibility, the level names used by this actuator differ from the names used by .NET. > > | Actuator level | .NET level | diff --git a/docs/docs/v4/management/prometheus.md b/docs/docs/v4/management/prometheus.md index d9122fc7..cf21220c 100644 --- a/docs/docs/v4/management/prometheus.md +++ b/docs/docs/v4/management/prometheus.md @@ -4,7 +4,7 @@ You can use the Prometheus endpoint to expose application metrics for collection The Steeltoe Prometheus endpoint configures the [OpenTelemetry Prometheus Exporter](https://opentelemetry.io/docs/languages/net/exporters/#prometheus) to behave like a Steeltoe management endpoint. -The Prometheus endpoint does not automatically instrument your application, but does make it easy to export metrics in the Prometheus metrics format, which can be used by tools like [Prometheus Server](https://prometheus.io/) and the [Metric Registrar](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/elastic-application-runtime/10-3/eart/metric-registrar-index.html) for Tanzu Platform for Cloud Foundry. +The Prometheus endpoint does not automatically instrument your application, but does make it easy to export metrics in the Prometheus metrics format, which can be used by tools like [Prometheus Server](https://prometheus.io/) and the [Metric Registrar](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/elastic-application-runtime/11-0/eart/metric-registrar-index.html) for Tanzu Platform for Cloud Foundry. See the [Steeltoe Management samples](https://github.com/SteeltoeOSS/Samples/blob/4.x/Management/src/ActuatorWeb/README.md) for more information about using this tool. @@ -140,7 +140,7 @@ docker run -d --name=prometheus -p 9090:9090 -v ./prometheus.yml:/etc/prometheus ### Tanzu Platform for Cloud Foundry -To emit custom metrics in Cloud Foundry, use [Metric Registrar](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/elastic-application-runtime/10-3/eart/metric-registrar-index.html). +To emit custom metrics in Cloud Foundry, use [Metric Registrar](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/elastic-application-runtime/11-0/eart/metric-registrar-index.html). > [!CAUTION] > Authenticated endpoints are not supported with Metric Registrar. diff --git a/src/Steeltoe.io/wwwroot/schema/latest/schema.json b/src/Steeltoe.io/wwwroot/schema/latest/schema.json index 6634b768..43fbfafd 100644 --- a/src/Steeltoe.io/wwwroot/schema/latest/schema.json +++ b/src/Steeltoe.io/wwwroot/schema/latest/schema.json @@ -1397,7 +1397,7 @@ }, "Duration": { "type": "integer", - "description": "Gets or sets the time (in milliseconds) to trace for, before automatically stopping the trace. Default value: 10." + "description": "Gets or sets how long to sample (in milliseconds). Higher values increase accuracy, at the cost of pausing the app for longer intervals. Default value: 10." }, "Enabled": { "type": "boolean", diff --git a/src/Steeltoe.io/wwwroot/schema/v4/schema.json b/src/Steeltoe.io/wwwroot/schema/v4/schema.json index 6634b768..43fbfafd 100644 --- a/src/Steeltoe.io/wwwroot/schema/v4/schema.json +++ b/src/Steeltoe.io/wwwroot/schema/v4/schema.json @@ -1397,7 +1397,7 @@ }, "Duration": { "type": "integer", - "description": "Gets or sets the time (in milliseconds) to trace for, before automatically stopping the trace. Default value: 10." + "description": "Gets or sets how long to sample (in milliseconds). Higher values increase accuracy, at the cost of pausing the app for longer intervals. Default value: 10." }, "Enabled": { "type": "boolean",