You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently templates are static set of roles and policies - the only variable being the domain name. The requirement from MH2 is to allow dynamic variables defined in the template where the caller can specify what those values should be.
We currently have domain which is replaced with the actual domain name. Now, we can additional variables into the template - e.g:
Currently templates are static set of roles and policies - the only variable being the domain name. The requirement from MH2 is to allow dynamic variables defined in the template where the caller can specify what those values should be.
We currently have domain which is replaced with the actual domain name. Now, we can additional variables into the template - e.g:
{code}
"paas_assertions": {
"policies": [
{
"name": "domain:policy._app__deploy",
"modified": "1970-01-01T00:00:00.000Z",
"assertions": [
{
"resource": "domain:daemon.service",
"role": "domain:role._app__deployer",
"action": "update”
}
]
}
]
}
{code}
So in this template we have three variables:
domain - user has no control over this one
service - service name
app - application name
So then zms-cli (which also needs to be updated along with the RDL,etc) will execute the following command:
zms-cli -d sports.site add-template paas_assertions app=api service=storage
Requirements:
The text was updated successfully, but these errors were encountered: