You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-functions/functions-create-first-java-maven.md
+13-1Lines changed: 13 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -79,6 +79,9 @@ Maven creates the project files in a new folder with a name of _artifactId_, whi
79
79
80
80
Open the new Function.java file from the *src/main/java* path in a text editor and review the generated code. This code is an [HTTP triggered](functions-bindings-http-webhook.md) function that echoes the body of the request.
81
81
82
+
> [!div class="nextstepaction"]
83
+
> [I ran into an issue](https://www.research.net/r/javae2e?tutorial=functions-maven-quickstart&step=generate-project)
84
+
82
85
## Run the function locally
83
86
84
87
Run the following command, which changes the directory to the newly created project folder, then builds and runs the function project:
@@ -114,6 +117,9 @@ Hello AzureFunctions!
114
117
```
115
118
The [function key](functions-bindings-http-webhook.md#authorization-keys) isn't required when running locally. Use `Ctrl+C` in the terminal to stop the function code.
116
119
120
+
> [!div class="nextstepaction"]
121
+
> [I ran into an issue](https://www.research.net/r/javae2e?tutorial=functions-maven-quickstart&step=local-run)
122
+
117
123
## Deploy the function to Azure
118
124
119
125
A function app and related resources are created in Azure when you first deploy your function app. Before you can deploy, use the [az login](/cli/azure/authenticate-azure-cli) Azure CLI command to sign in to your Azure subscription.
@@ -142,6 +148,9 @@ The deployment also packages the project files and deploys them to the new funct
142
148
143
149
After the deployment completes, you see the URL you can use to access your function app endpoints. Because the HTTP trigger we published uses `authLevel = AuthorizationLevel.FUNCTION`, you need to get the function key to call the function endpoint over HTTP. The easiest way to get the function key is from the [Azure portal].
144
150
151
+
> [!div class="nextstepaction"]
152
+
> [I ran into an issue](https://www.research.net/r/javae2e?tutorial=functions-maven-quickstart&step=deploy)
153
+
145
154
## Get the HTTP trigger URL
146
155
147
156
<!--- We can updates this to remove portal dependency after the Maven archetype returns the full URLs with keys on publish (https://github.com/microsoft/azure-maven-plugins/issues/571). -->
@@ -172,6 +181,9 @@ This sends a POST request to the function endpoint with `AzureFunctions` in the
172
181
Hello AzureFunctions!
173
182
```
174
183
184
+
> [!div class="nextstepaction"]
185
+
> [I ran into an issue](https://www.research.net/r/javae2e?tutorial=functions-maven-quickstart&step=verify-deployment)
186
+
175
187
## Next steps
176
188
177
189
You've created a Java functions project with an HTTP triggered function, run it on your local machine, and deployed it to Azure. Now, extend your function by...
@@ -181,4 +193,4 @@ You've created a Java functions project with an HTTP triggered function, run it
0 commit comments