This message was deleted.

actually, i see

azure:HttpFunction

is the name of itself, and it's extending

pulumi.ComponentResource

trying to see how that maps back so I can change the triggers. Any docs around this?

There is some work on supporting this sort of scenario more nicely in https://github.com/pulumi/pulumi-azure-serverless. But I’m not sure that yet includes support for timer sources. We’ll be fleshing our remaining event sources as part of moving this into the core azure package soon. Note that you can always put together the underlying Azure resources yourself to do this - but there’s enough boilerplate that we have tried to add some useful “sugar” here in general. /cc @lemon-spoon-91807 in case he has any other pointers that could be useful.

Yup. This is something we do want to improve.

thanks guys, Ive been going through the AZ functions.. and, wow.. complex. When I was installing packages via a windows based console I started to ponder alternatives. I'm going to run this through AWS lambda instead for the time being, I just need a simple cron-link function running and that will be the quickest path for now 👍

@brave-angle-33257 I've made that repo public now - we had been releasing the component at https://www.npmjs.com/package/@pulumi/azure-serverless but we had apparently not made the repo itself public.

Thanks @white-balloon-205!