azure-docs VS twitter-lite

Explained here: https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-alternate-dpm-server.md

Official doc on runbook limitations: https://github.com/MicrosoftDocs/azure-docs/blob/main/includes/azure-automation-service-limits.md

I dont think that works:

    > git clone --depth 1 https://github.com/MicrosoftDocs/azure-docs

Does anyone have any idea why this is? I found a github issue that basically describes the issue as well but there is no satisfying solution. Can you really not use native azure monitoring solutions if you migrate your VMs to azure? That seems hard to believe and I hope I'm just missing something. I'm very thankful for any advice at this point.

It appears that there is a 512kb payload limit with runbook webhooks, which I can only find mention of on this git file:https://github.com/MicrosoftDocs/azure-docs/blob/main/includes/azure-automation-service-limits.mdThe data I was including in the web activity body appears to be just under this limit and would trigger the runbook without issue. But with the extra data webhook activities include in the body it puts it over the limit and never triggers it. Unfortunately Data Factory doesn't handle this situation properly and the activity runs indefinitely until you cancel it (despite the timeout configured).The work around for me was to add a foreach activity and put the webhook activity inside of that.

Follow the OAuth authentication section in the twitter-lite README as that is the package you are using.

Twitter Lite is a tiny, full-featured, flexible server library for Twitter APIs.

The library and its documentation can be found on Github

Take a look at this JavaScript library: https://github.com/draftbit/twitter-lite

Download twitter-lite to interact with Twitter's API: yarn add twitter-lite

I finally ended up with twitter-lite that has TypeScript support and takes over the burden of authentication.

twitter-lite - lightweight library for Twitter API