From f542d491faf4a59a6e7902678d9f90621f85366e Mon Sep 17 00:00:00 2001 From: Leif Madsen Date: Mon, 5 Jul 2021 15:21:02 -0400 Subject: [PATCH] Use empty list vs object for clouds parameter (#232) The use of an empty clouds object results in an error in Service Telemetry Operator since a list is expected. Using an empty list will result in the expected outcome of no Smart Gateways being defined rather than an error. Resolves: rhbz#1979376 --- .../modules/proc_deleting-the-default-smart-gateways.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc-Service-Telemetry-Framework/modules/proc_deleting-the-default-smart-gateways.adoc b/doc-Service-Telemetry-Framework/modules/proc_deleting-the-default-smart-gateways.adoc index 593fb08a..8dec3e88 100644 --- a/doc-Service-Telemetry-Framework/modules/proc_deleting-the-default-smart-gateways.adoc +++ b/doc-Service-Telemetry-Framework/modules/proc_deleting-the-default-smart-gateways.adoc @@ -26,7 +26,7 @@ [role="_abstract"] After you configure {ProjectShort} for multiple clouds, you can delete the default Smart Gateways if they are no longer in use. The Service Telemetry Operator can remove `SmartGateway` objects that have been created but are no longer listed in the ServiceTelemetry `clouds` list of objects. You can enable the removal of SmartGateway objects that are not defined by the `clouds` parameter by setting `cloudsRemoveOnMissing: true` in the `ServiceTelemetry` manifest. -TIP: If you do not want any Smart Gateways deployed, define an empty clouds object using the `clouds: {}` parameter. +TIP: If you do not want to deploy any Smart Gateways, define an empty clouds list by using the `clouds: []` parameter. WARNING: The `cloudsRemoveOnMissing` parameter is disabled by default. If you enable the `cloudsRemoveOnMissing` parameter, you remove any manually created `SmartGateway` objects in the current namespace without any possibility to restore.