From d723d407d9553b5246853d4c791adcfca3a56cf9 Mon Sep 17 00:00:00 2001 From: Mark Boyd Date: Wed, 11 Oct 2023 11:41:59 -0400 Subject: [PATCH] remove sorting logic --- _docs/services/intro.md | 8 ++++---- _docs/services/relational-database.md | 8 ++++---- _includes/sidenav.html | 2 +- 3 files changed, 9 insertions(+), 9 deletions(-) diff --git a/_docs/services/intro.md b/_docs/services/intro.md index 8d7f48de9..92e2c2d5f 100644 --- a/_docs/services/intro.md +++ b/_docs/services/intro.md @@ -8,7 +8,7 @@ redirect_from: - /docs/services/ - /docs/pricing/managed-services-cost/ --- -You can expand the functionality of your cloud.gov application by making use of services. Before your application can use a service, you must provision the service and supply the credentials for using the service to your application. +You can expand the functionality of your cloud.gov application by making use of services. Before your application can use a service, you must provision the service and supply the credentials for using the service to your application. There are two ways to provision services: @@ -16,7 +16,7 @@ There are two ways to provision services: * **Managed service instances**: You can provision a [managed service instance](https://docs.cloudfoundry.org/devguide/services/#instances) through the marketplace in cloud.gov on demand, and let cloud.gov supply the credentials. ## When to use a user-provided service -User-provided services enable developers to use services that are not available in the marketplace with their apps running on Cloud.gov. +User-provided services enable developers to use services that are not available in the marketplace with their apps running on Cloud.gov. If the provisioning of the service is not automated or already existent, you should set up a user-provided service. @@ -47,7 +47,7 @@ cf cups -p '{"username":"admin","password":"pa55woRD"}' cloud.gov offers a marketplace of FedRAMP-authorized [managed services]({{ site.baseurl }}{% link _docs/deployment/managed-services.md %}) that we operate in a secure and compliant manner on your behalf. You can also [extend the marketplace](#extending-the-marketplace) to include additional services run by other organizations. -To list all the managed services and plans available to a given space, you run `cf marketplace` from your command line. Here is a list of the managed services that are generally available: +To list all the managed services and plans available to a given space, you run `cf marketplace` from your command line. Here is a list of the managed services that are generally available: {% assign cgservices = site.data.services %} @@ -78,7 +78,7 @@ To list all the managed services and plans available to a given space, you run ` ### Extending the marketplace -"Brokers" are the invisible integrators that enable you to set up managed service instances in cloud.gov in a consistent and self-service fashion. A broker offers a simple API that manages the service instance lifecycle. You can run your own broker to make a service from outside cloud.gov available through cloud.gov's marketplace. +"Brokers" are the invisible integrators that enable you to set up managed service instances in cloud.gov in a consistent and self-service fashion. A broker offers a simple API that manages the service instance lifecycle. You can run your own broker to make a service from outside cloud.gov available through cloud.gov's marketplace. *Note that when you extend the cloud.gov marketplace with your own broker, the cloud.gov team cannot vouch for the security or compliance of the brokered services. You will need to document and authorize your own brokered services in accordance with your agency's compliance requirements.* diff --git a/_docs/services/relational-database.md b/_docs/services/relational-database.md index 68cfa125f..6c24d2236 100644 --- a/_docs/services/relational-database.md +++ b/_docs/services/relational-database.md @@ -250,9 +250,9 @@ Name | Description | `storage` | Number of GB available to the database instance | `backup_retention_period` | Specifies a number of days to retain daily snapshots. | `binary_log_format` | Specifies the format for [MySQL binary logging](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_LogAccess.MySQL.BinaryFormat.html). **Only supported for MySQL database plans**. Valid options: `ROW`, `STATEMENT`, `MIXED`. | -`enable_pg_cron` | Boolean to enable [`pg_cron` extension on PostgreSQL databases](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/PostgreSQL_pg_cron.html) (requires PostgreSQL 12.5 and above) | false | -`enable_functions` | Boolean to enable functions, procedures, and triggers on MySQL databases | false | -`storage_type` | [RDS storage type to use for the database](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_Storage.html). Valid options: `gp3` | false | +`enable_pg_cron` | Boolean to enable [`pg_cron` extension on PostgreSQL databases](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/PostgreSQL_pg_cron.html) (requires PostgreSQL 12.5 and above) | +`enable_functions` | Boolean to enable functions, procedures, and triggers on MySQL databases | +`storage_type` | [RDS storage type to use for the database](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_Storage.html). Valid options: `gp3` | #### Examples of optional parameters @@ -299,7 +299,7 @@ cf update-service ${SERVICE_NAME} \ -c '{"storage_type": "gp3"}' ``` -**Please note that databases must be at least 20 GB in size to use `gp3` as the storage type.**. If you get an error during the update about your databse storage size, try specifying a minimum value of `20` for `storage` in the `update-service` command: +**Please note that databases must be at least 20 GB in size to use `gp3` as the storage type.** If you get an error during the update about your database storage size, try specifying a minimum value of `20` for `storage` (you can also choose a larger value) in the `update-service` command: ```sh cf update-service ${SERVICE_NAME} \ diff --git a/_includes/sidenav.html b/_includes/sidenav.html index 478677119..bafe06743 100644 --- a/_includes/sidenav.html +++ b/_includes/sidenav.html @@ -61,4 +61,4 @@ {%- endfor -%} - \ No newline at end of file +