Apply Config in UI vs. API
Posted: Wed Apr 15, 2020 10:43 pm
If there is any difference, what is the difference between how an Apply Configuration is applied on the backend when executed through the UI, versus submitted through an API call?
To give more details on what i mean by both scenarios,
UI - by executing an Apply Config through this method, API Call - When sending an add or delete host API call by appending the applyconfig=1 parameter at the end i feel like when applyconfig=1 is appended to an add/delete API call, i see the result of it through the UI significantly faster than when manually applying the config, but i need to confirm if this is just in my head, or if there really is a difference. Thanks for reading my silly question up to this point.
To give more details on what i mean by both scenarios,
UI - by executing an Apply Config through this method, API Call - When sending an add or delete host API call by appending the applyconfig=1 parameter at the end i feel like when applyconfig=1 is appended to an add/delete API call, i see the result of it through the UI significantly faster than when manually applying the config, but i need to confirm if this is just in my head, or if there really is a difference. Thanks for reading my silly question up to this point.