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
Is your feature request related to a problem? Please describe.
Currently, to store configurations in the config store, each must be stored individually with a separate RPC request. This can be very time-intensive when storing a large number of files. While testing automated deployment of a building with 1000+ device entries, ansible needed an hour to install them all.
A similar problem occurs with the web API (when managing devices) because it must request all these files using the management methods; first requesting a list and then requesting each individual file. This is not as time consuming as storing the files, but still slows down considerably for large device sets.
Describe the solution you'd like
The Configuration Store should have RPC methods for storing and retrieving multiple configurations at once. When these methods are called, all of the updates would be made in a single round-trip, and callbacks would not be triggered until the process is complete.
These should be available as "manage" methods to support use cases such as the web API.
Describe alternatives you've considered
The storing of many files simultaneously could be done by directly modifying the configuration store JSON file, but this probably would not be able to update the agent if it were running, and violates the expectation of the configuration store service itself.
The web API use case could probably be supported by new methods on the driver agent itself instead of interacting with the configuration store.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently, to store configurations in the config store, each must be stored individually with a separate RPC request. This can be very time-intensive when storing a large number of files. While testing automated deployment of a building with 1000+ device entries, ansible needed an hour to install them all.
A similar problem occurs with the web API (when managing devices) because it must request all these files using the management methods; first requesting a list and then requesting each individual file. This is not as time consuming as storing the files, but still slows down considerably for large device sets.
Describe the solution you'd like
The Configuration Store should have RPC methods for storing and retrieving multiple configurations at once. When these methods are called, all of the updates would be made in a single round-trip, and callbacks would not be triggered until the process is complete.
These should be available as "manage" methods to support use cases such as the web API.
Describe alternatives you've considered
The storing of many files simultaneously could be done by directly modifying the configuration store JSON file, but this probably would not be able to update the agent if it were running, and violates the expectation of the configuration store service itself.
The web API use case could probably be supported by new methods on the driver agent itself instead of interacting with the configuration store.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: