From 21a014a122c87bf32e3bc8a4d57120ce25a7b625 Mon Sep 17 00:00:00 2001 From: Saravanan KR Date: Fri, 16 Feb 2018 16:20:25 +0530 Subject: [PATCH] Modify the document to look for warning for role-specific parameter When a parameter is not supported as role-specific input in the service implementation, then a warning will be shown during the deployment. Modify the document to reflect this message. Change-Id: I8b60d95b26d62d7ff9b241de27c5f6776ae2d911 Depends-On: Id2799babe496e742e1e47dfc2b2d1cf1dee61071 --- .../advanced_deployment/role_specific_parameters.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/source/install/advanced_deployment/role_specific_parameters.rst b/doc/source/install/advanced_deployment/role_specific_parameters.rst index 1142a054..8ba11573 100644 --- a/doc/source/install/advanced_deployment/role_specific_parameters.rst +++ b/doc/source/install/advanced_deployment/role_specific_parameters.rst @@ -59,6 +59,6 @@ which will be done by the service implementation:: As of now, not all parameters can be set per role, it is based on the service or template implementation. Each service should have the implementation to merge the global parameters and role-specific - parameters, as explained in the above example. And today, not all services - have this merging logic, check the parameter usage before using it as - role-specific. + parameters, as explained in the above example. A warning will be shown + during the deployment, if an invalid parameter (which does not support + role-specific implementation) is provided as role-specific input.