Extensions with scheduled triggers not supported. PR created ✔

[stfsy]

[REQUIRED] Environment info

firebase-tools: 11.19.0

Platform: Windows

[REQUIRED] Test case

There is a new unit test case in #5373

[REQUIRED] Steps to reproduce

• Use a Windows machine
• Install firebase-tools
• Install firestore-counter extension
• Start the emulator
• Logs say that function controllerCore was ignored because of an unknown trigger

[REQUIRED] Expected behavior

Extensions with scheduled trigger are also supported by the emulator.

[REQUIRED] Actual behavior

Extensions with scheduled trigger are also supported by Emulator.

The triggerHelper module defines which triggers are supported. The scheduleTrigger is currently not handled and therefore not supported.

firebase-tools/src/extensions/emulator/triggerHelper.ts

Lines 33 to 47 in 86a5ba1

	if (properties.httpsTrigger) {
	etd.httpsTrigger = properties.httpsTrigger;
	}
	if (properties.eventTrigger) {
	etd.eventTrigger = {
	eventType: properties.eventTrigger.eventType,
	resource: properties.eventTrigger.resource,
	service: getServiceFromEventType(properties.eventTrigger.eventType),
	};
	} else {
	EmulatorLogger.forEmulator(Emulators.FUNCTIONS).log(
	"WARN",
	`Function '${resource.name} is missing a trigger in extension.yaml. Please add one, as triggers defined in code are ignored.`
	);
	}

To be able to use extensions like firebase-counter in the emulator and without modifications we need support for scheduleTriggers. I created PR #5373 which converst the scheduleTrigger to a pubSub trigger which in turn can be triggered by writing to the pubsub topic.

[google-oss-bot]

This issue does not have all the information required by the template. Looks like you forgot to fill out some sections. Please update the issue with more information.

[stfsy]

@polarby because of firebase/extensions#876, i saw you are also using the counter extension in the emulator. Thought you might be interested as well

[polarby]

If you need to run functions with a low frequency (once every hour/day..) you can usually run those functions manually (as you also most likely won't have the emulator running for that time). Tasks that require high-frequency emulation, will be more challenging to handle and likely need support for scheduled functions from the firebase team.

Low-frequency functions (manual emulation)

Run the terminal in your project directory

$  firebase functions:shell

It will show all your callable functions, including your scheduled ones. Run those by calling them:

yourScheduledFunc();

[stfsy]

@polarby thank you. Appreciate it.

In this case the controllerCore function is not even recognized as a callable function by the emulator. It is completey ignored because of the unknown trigger and therefore does not get loaded/instantiated at all 😞

[polarby]

Yeah, that sure is a Problem. A workaround for now (and not too time-consuming) is for sure to copy-paste the source code of those emulated functions and then run them. But let's keep this issue open for the implementation of this essential feature!

[stfsy]

Would it make sense to merge my PR in the mean time? Its not very invasive and at least enables the emulator to parse and instantiate the function, so that It can be triggered from the parent application without copying the source code.

[joehan]

Thanks for the contribution! Closing this since you added support.
We don't have any plans to real scheduled support to the emulator suite. Since most schedules are pretty impractical in an emulated environment, it makes more sense to manually trigger these functions for testing.