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
As per urbanriskmap/riskmap#32
I would suggest we go straight to a scheduled lambda function rather than putting it in as part of reports, however. I guess for that, and for transforming qlue, etc. down the track, have them still as submodules of this reports master repo, and then this repo can package them (ala https://github.com/urbanriskmap/aws-lambda-image/blob/master/Makefile ) and document them? Leaving the powertrack as the odd one out.
The text was updated successfully, but these errors were encountered:
As per
urbanriskmap/riskmap#32
I would suggest we go straight to a scheduled lambda function rather than putting it in as part of reports, however. I guess for that, and for transforming qlue, etc. down the track, have them still as submodules of this reports master repo, and then this repo can package them (ala https://github.com/urbanriskmap/aws-lambda-image/blob/master/Makefile ) and document them? Leaving the powertrack as the odd one out.
The text was updated successfully, but these errors were encountered: