python-pub | python获取所有qq好友、全部群所有成员部分信息，并保存列表至电子表格

Looking at the role definition of EventGrid EventSubscription Contributor, it does not have the permission to perform Microsoft.EventGrid/topics/write action. Only following actions are allowed:

you can mitigate the issue using --no-bundler while publishing.

Here is the explanation.

during a general publish using --build-native-deps, we try to use Pyinstaller to bundle all the custom dependencies specified in your requirements.txt together with our runner (worker). We started to do this in an effort to improve startup performance that you get after publishing to Azure Functions. Although, this process has been flaky and we are planning on moving away from it.

--no-bundler flag bypasses that bundling process. So, we do not use Pyinstaller or any such module to do temporary optimizations. The caveat is that you may experience slight linger delay (cold start) when hitting your API end-point.

I was able to solve this by installing docker on my local machine and using the CLI commands to build and deploy to azure function app -

func azure functionapp publish --build-native-deps

First, if I understand correctly by what you are showing in your output, you are using a Pub/Sub notification to send a message whenever you make changes to a Cloud Storage object. This information could be helpful.

Now, message.data["name"] is not going to work because message.data is a BYTES object. Thus, can't be indexed as a dict.

To treat it as a dict, you first have to decode it as base64 (import base64). After that, what you are left is a string which looks like JSON format. You then use json.load() (don't forget to import json) to transform this string into a dict. Now you can index the message.

The code for this will be: