Get Indices End of Day (EOD) historical data from Yahoo

[kjooleng]

First attempt

[kjooleng]

Feel free to comment. It can be modified to handle other data sources. No idea why the node links are broken

[kjooleng]

@Benjamin_Behrens

you could parameterize the schedule node or add a database lookup for trigger times instead of hard-coding 0806 hrs

Noted. Reason it was hard coded at 0806 hours as I needed to space out the workflow to avoid clashing with other workflows

@Benjamin_Behrens

are you handling partial days or halted trading hours automatically

I believe this is not relevant as I am retrieving EOD data historically

@Benjamin_Behrens

curious about the aggregation logic

I am using the aggregate node so that X attachments can be sent within one email, instead of X emails

[kjooleng]

Great! Workflows working as intended

[kjooleng]

Due to changes in Alpine image, apk is no longer supported

Trying to find other workaround

[kjooleng]

This is the workaround

Thanks to @Anshul_Namdev

Powershell support for v3.0

That log says apk itself starts now, and the failure has moved into the package database. Every constraint in it has the form name><Q1..., which is apk’s identity-hash pin, and the world file in the current image pins every installed package to its exact hash. COPY --from=alpine:3.22 /lib/apk /lib/apk replaces the installed-package database with the one from a stock 3.22 image, so apk no longer knows nodejs-26, librdkafka or openssh are installed, tries to pull them from the 3.24 repo, and none…