azure-functions
Here are 1,242 public repositories matching this topic...
-
Updated
Aug 26, 2020 - C#
-
Updated
Oct 21, 2020 - C#
-
Updated
Nov 10, 2020 - C#
-
Updated
Aug 5, 2020
-
Updated
Nov 8, 2020 - C#
There is a gap in the docs about managing your installation using github settings and imgbot settings
Main points:
For managing your imgbot installation check out github's docs.
They offer 2 options for managing this. You can select which repositories you want it installed in, or you can choose "all repositories including all future repositories".
You can log in and see your repos and req
I'm getting "authLevel": "Anonymous" from using the new -a flag. This causes warnings from the JSON schema and has caused an issue with an app where it defaults back to function level when published. That last part strikes me as especially strange but would be a host issue. Regardless, the output from the Core Tools should be camelCased instead of PascalCased.
-
Updated
Sep 5, 2020 - JavaScript
-
Updated
Nov 3, 2020 - C#
-
Updated
Jun 24, 2018 - Shell
-
Updated
Oct 8, 2020
-
Updated
Apr 20, 2018
-
Updated
Oct 3, 2020 - Python
-
Updated
Nov 10, 2020 - JavaScript
-
Updated
Sep 10, 2020 - C#
-
Updated
Nov 10, 2020 - C#
-
Updated
Aug 4, 2020 - Python
-
Updated
Nov 9, 2020 - Python
-
Updated
Dec 5, 2017 - JavaScript
-
Updated
Jan 17, 2019 - TypeScript
-
Updated
Feb 14, 2019 - C#
-
Updated
Sep 29, 2020 - JavaScript
Improve this page
Add a description, image, and links to the azure-functions topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the azure-functions topic, visit your repo's landing page and select "manage topics."
Hello,
As a result of #5621, Serverless-created buckets include a bucket policy that is supposed to deny any
s3:*Action over that bucket, unless it is performed over HTTPS.Unfortunately that Bucket policy is incomplete and still allows listing the Bucket content over insecure HTTP connection, if the Principal has permissions to perform that action.
Incorrect (current) Bucket Policy: