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.
We currently need to specify the dataset IDs inside the lambda functions. This means, we have to deploy a new version each time a dataset ID changes. It bears also the risk, that we forget to update the code, when we make changes to the datasets.
Describe the solution you'd like
Instead of hardcoding the ID into the lambda function, make a call to a central table which holds all the relevant information.
This way we can assure that IDs get propagated to all apps, once they change.
(We need to create this central table first before we can start working on this ticket.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
We currently need to specify the dataset IDs inside the lambda functions. This means, we have to deploy a new version each time a dataset ID changes. It bears also the risk, that we forget to update the code, when we make changes to the datasets.
Describe the solution you'd like
Instead of hardcoding the ID into the lambda function, make a call to a central table which holds all the relevant information.
This way we can assure that IDs get propagated to all apps, once they change.
(We need to create this central table first before we can start working on this ticket.
The text was updated successfully, but these errors were encountered: