dtcarls
commented
5 years ago I 100% agree it fits that architecture perfectly and debated implementing it over the summer. However the barrier to entry then gets higher for the casual commissioner. I am still potentially interested in doing it in another branch just for the exercise of it and potentially pull into master if I can get it as close as possible to the “push button” setup.
On Thu, Aug 29, 2019 at 2:57 PM Mikael Stadden notifications@github.com wrote:
These scheduled messages seem like an ideal use case for running as scheduled, serverless function in order to minimize the amount of compute needed to run this workload. Also management would be easier as there would be no need to keep the process running.
Is there any interest in some basic scaffolding code and documentation around getting this to code to work as a scheduled Azure Function? Ideally there would be an easy deployment script (terraform, bash, powershell, whatever) that folks can run to handle the deployment.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/dtcarls/ff_bot/issues/33?email_source=notifications&email_token=ACWGOWKGRMMXYL4P5LLM6FLQHALZLA5CNFSM4ISFXJN2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HII5GGQ, or mute the thread https://github.com/notifications/unsubscribe-auth/ACWGOWPJ4YMVVTHAH2HIRRDQHALZLANCNFSM4ISFXJNQ .
mikaelweave
These scheduled messages seem like an ideal use case for running as scheduled, serverless function in order to minimize the amount of compute needed to run this workload. Also management would be easier as there would be no need to keep the process running.
Is there any interest in some basic scaffolding code and documentation around getting this to code to work as a scheduled Azure Function? Ideally there would be an easy deployment script (terraform, bash, powershell, whatever) that folks can run to handle the deployment.