Non documented functionality in the tasks api

Help
1

Hi i noticed it is possible to make a provision execute within the /tasks api with the arguments:
{
name: “provisions”,
provisions: [“my_provision_name”, “argument1”, “argument2”,…],
}

Is this feature still supported?

2

I’ve searched the documentation and reviewed the code and see no way of directly applying a provision to a specific CPE. The supported way is to apply a provision to a CPE is via presets.

3

image
image1520×1270 188 KB

During the validation of tasks there was a “provisiosn” clause and i started following the code from there. Seems to be implemented in this commit: Implement support for Get/SetParameterAttributes · genieacs/genieacs@bf9517c · GitHub

I tested in my setup and it seems to be working…

4

Thank you for that. I missed the calls in api-functions when searching through the code. If you have time, can you please create a PR to update the docs with information about how to call a provision on a CPE directly from the API? I’d put it under the “download” section on this page

5

Sure, I’m developing a feature in my internal project that makes use of this feature. I’ll get some personal experience and document it.

1 Like