Optimize package data associations for LoRa Cloud Modem & Geolocation Services

[cvetkovski98]

Summary

Each application package has configuration data stored in a DefaultPackageAssociation and a PackageAssociation. The values in the PackageAssociation are used to override the DefaultPackageAssociation values per device. We should optimize the data stored in the PackageAssociation by reducing the number of fields we persist in the underlying data.

Follows up #6317

Current Situation

The PackageAssociation(s) for the integrations related to LoRa Cloud Modem & Geolocation Services currently store all the fields that are required in the DefaultPackageAssociation to enable (de)serialization to and from structpb.Struct{} and proper validation. This solution might create residual PackageAssociation(s) that bring no actual value to the integration (e.g. data that contains "token": "").

Why do we need this? Who uses it, and when?

Reduce the amount of data we store in Redis related to the integrations for LoRa Cloud Modem & Geolocation Services.

Proposed Implementation

Improve the (de)serialization from and to structpb.Struct{} by allowing nilable data fields in the DefaultPackageAssociation and PackageAssociation. Move the layer of data validation after merging the configurations instead of during.

Contributing

• I can help by doing more research.
• I can help by implementing the feature after the proposal above is approved.
• I can help by testing the feature before it's released.

Code of Conduct

• I agree to follow TTN's Community Code of Conduct.