Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error raised when creating new HttpTrigger function on CLI v4

See original GitHub issue

As per @anthonychu’s blog post - https://techcommunity.microsoft.com/t5/apps-on-azure/announcing-azure-functions-4-0-public-preview-with-net-6-support/ba-p/2772098 - I have updated my v4 core tools.

On creating a new HttpTrigger function I receive the following error:

The post action 84c0da21-51c8-4541-9940-6ca19af04ee6 is not supported.
Description: Opens the function class file in the editor

Steps to reproduce

cd c:\temp
mkdir functions8
cd functions8
func init --worker-runtime dotnetIsolated
func new
select HttpTrigger from option list
Add name of function eg. MyFunction

Results

C:\Temp\functions8> func new
Use the up/down arrow keys to select a template:Function name: MyFunction
MyFunction
The post action 84c0da21-51c8-4541-9940-6ca19af04ee6 is not supported.
Description: Opens the function class file in the editor

The function "MyFunction" was created successfully from the "HttpTrigger" template.

SDKs installed

C:\Temp\functions8> dotnet --list-sdks 2.2.401 [C:\Program Files\dotnet\sdk] 3.1.301 [C:\Program Files\dotnet\sdk] 3.1.406 [C:\Program Files\dotnet\sdk] 5.0.103 [C:\Program Files\dotnet\sdk] 5.0.401 [C:\Program Files\dotnet\sdk] 6.0.100-preview.6.21355.2 [C:\Program Files\dotnet\sdk] 6.0.100-rc.1.21458.32 [C:\Program Files\dotnet\sdk]

Issue Analytics

State:
Created 2 years ago
Comments:8 (5 by maintainers)

Top GitHub Comments

1reaction

soninarencommented, Oct 7, 2021

Interestingly, well I thought it was, I just ran the same command in the developer terminal inside Visual Studio 2022 Preview 4.1 half expecting the post action to execute and open the newly creating function in the IDE instance but the same error occurred.

This is expected. If the command was executed via dotnet cli, regardless of the kind of terminal window.

The only time this post action actually takes effect is when it is run via the VS UI. So if you add a function to your project via VS, right click csproj -> Add a function -> (follow wizard until function creation). This is when you would see the newly created function in editor.

1reaction

anthonychucommented, Sep 25, 2021

Thanks for reporting. @brettsam @soninaren can we suppress this message?