At the moment, when the front end loads up their new (to-be-created) sensor initialization, they will need a way to pre-populate the page with the already-existing sensor initialization information.
This will use the already-existing sensorNetworkConfig repository. The following other tasks will need to be executed:
[ ] Create a sensorNetworkConfig contract folder
[ ] Create a RetrieveByTelescopeId class that
[ ] Retrieves the config by its radioTelescopeId.
We do not want to retrieve it by its id.
[ ] Create a UserRadioTelescopeConfigWrapper class
[ ] Require user roles USER and ADMIN for function retrieveByTelescopeId
[ ] Create a SensorNetworkConfigFactory interface
[ ] Create function retrieveByTelescopeId of return type Command<SensorNetworkConfig, Multimap<ErrorTag, String>>
[ ] Create a sensorNetworkConfig controller folder
[ ] Create a class `SensorNetworkConfigRetrieveController
[ ] Through the wrapper, call retrieveByTelescopeId, passing the ID as a parameter
[ ] Error check as necessary (id not found, user roles invalid, etc)
[ ] Use SpectracyberConfigRetrieveController.kt for inspiration
TEST, using Postman, that when you pass a telescope ID through this API call, it returns the correct (and complete) sensor network config data.
Be sure to create unit tests for functions in the Controller, Contract, and any other functions that may have been created over the course of this issue.
At the moment, when the front end loads up their new (to-be-created) sensor initialization, they will need a way to pre-populate the page with the already-existing sensor initialization information.
This will use the already-existing
sensorNetworkConfigrepository. The following other tasks will need to be executed:sensorNetworkConfigcontract folderRetrieveByTelescopeIdclass thatradioTelescopeId.id.UserRadioTelescopeConfigWrapperclassUSERandADMINfor functionretrieveByTelescopeIdSensorNetworkConfigFactoryinterfaceretrieveByTelescopeIdof return typeCommand<SensorNetworkConfig, Multimap<ErrorTag, String>>sensorNetworkConfigcontroller folderretrieveByTelescopeId, passing the ID as a parameterSpectracyberConfigRetrieveController.ktfor inspirationTEST, using Postman, that when you pass a telescope ID through this API call, it returns the correct (and complete) sensor network config data.
Be sure to create unit tests for functions in the Controller, Contract, and any other functions that may have been created over the course of this issue.