@@ -27,7 +27,7 @@ For illustration, please refer to the following example.
2727 "scheduling_priority" : " 0" ,
2828 "uid" : 1000 ,
2929 "gid" : 1000 ,
30- "supplementary_group_ids" : [500 , 600 , 700 ],
30+ "supplementary_group_ids" : [500 , 600 , 700 ]
3131 }
3232 }
3333}
@@ -154,6 +154,9 @@ All time periods will be configured in seconds. If a smaller time period is need
154154 "is_self_terminating" : false ,
155155 "is_state_manager" : false ,
156156 "depends_on" : []
157+ },
158+ "run_target" : {
159+ "transition_timeout" : 2
157160 }
158161 },
159162 "components" : {
@@ -215,7 +218,8 @@ All time periods will be configured in seconds. If a smaller time period is need
215218 },
216219 "Full" : {
217220 "description" : " Everything running" ,
218- "includes" : [" Minimal" , " test_app1" ]
221+ "includes" : [" Minimal" , " test_app1" ],
222+ "transition_timeout" : 5
219223 },
220224 "Off" : {
221225 "description" : " Nothing is running"
@@ -254,4 +258,4 @@ Should we reserve a name for the initial RunTarget or make this configurable (se
254258
255259### Defining json schema
256260
257- After agreement on the rough structure, we will define a json schema depicting all possible configuration options.
261+ After agreement on the rough structure, we will define a json schema depicting all possible configuration options.
0 commit comments