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
This commit is contained in:
parent
a0ef3ff84b
commit
21a014a122
@ -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
|
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
|
service or template implementation. Each service should have the
|
||||||
implementation to merge the global parameters and role-specific
|
implementation to merge the global parameters and role-specific
|
||||||
parameters, as explained in the above example. And today, not all services
|
parameters, as explained in the above example. A warning will be shown
|
||||||
have this merging logic, check the parameter usage before using it as
|
during the deployment, if an invalid parameter (which does not support
|
||||||
role-specific.
|
role-specific implementation) is provided as role-specific input.
|
||||||
|
Loading…
Reference in New Issue
Block a user