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
summary: Use a unified configuration model to define datasources for Java Database Connectivity (JDBC) and Reactive drivers.
33
-
categories: "getting-started, data"
33
+
categories: "data, getting-started"
34
34
id: datasources
35
35
type: reference
36
36
url: /guides/datasource
@@ -55,7 +55,7 @@ types:
55
55
- title: Logging configuration
56
56
filename: logging.adoc
57
57
summary: "Read about the use of logging API in Quarkus, configuring logging output, and using logging adapters to unify the output from other logging APIs."
58
-
categories: "getting-started, core"
58
+
categories: "core, getting-started"
59
59
id: logging
60
60
type: reference
61
61
url: /guides/logging
@@ -152,21 +152,21 @@ types:
152
152
- title: Authentication mechanisms in Quarkus
153
153
filename: security-authentication-mechanisms.adoc
154
154
summary: "The Quarkus Security framework supports multiple authentication mechanisms, which you can use to secure your applications."
155
-
categories: "security, web"
155
+
categories: "web, security"
156
156
id: security-authentication-mechanisms
157
157
type: concepts
158
158
url: /guides/security-authentication-mechanisms
159
159
- title: Basic authentication
160
160
filename: security-basic-authentication.adoc
161
161
summary: HTTP Basic authentication is one of the least resource-demanding techniques that enforce access controls to web resources.
162
-
categories: "security, web"
162
+
categories: "web, security"
163
163
id: security-basic-authentication
164
164
type: concepts
165
165
url: /guides/security-basic-authentication
166
166
- title: "Duplicated context, context locals, asynchronous processing and propagation"
167
167
filename: duplicated-context.adoc
168
168
summary: "When using a traditional, blocking, and synchronous framework, processing of each request is performed in a dedicated thread."
summary: Secure HTTP access to Jakarta REST (formerly known as JAX-RS) endpoints in your application with Bearer token authentication by using the Quarkus OpenID Connect (OIDC) extension.
summary: "To protect your web applications, you can use the industry-standard OpenID Connect (OIDC) Authorization Code Flow mechanism provided by the Quarkus OIDC extension."
summary: "With the Quarkus OpenID Connect (OIDC) extension, you can protect application HTTP endpoints by using the OIDC Authorization Code Flow mechanism."
summary: Secure your Quarkus application endpoints by combining the built-in Quarkus Basic authentication with the Jakarta Persistence identity provider to enable role-based access control (RBAC).
a| https://github.com/quarkusio/quarkus/blob/main/extensions/vertx-http/deployment/src/main/java/io/quarkus/vertx/http/deployment/EagerSecurityInterceptorBuildItem.java[`io.quarkus.vertx.http.deployment.EagerSecurityInterceptorBuildItem`, window="_blank"] :: +++Bears collected security interceptors per method candidate. Methods are candidates because not each of them must be finally resolved to endpoint and invoked. <p> This build item should be consumed by every extension that run s before CDI interceptors when proactive auth is disabled.+++
a| https://github.com/quarkusio/quarkus/blob/main/extensions/vertx-http/deployment/src/main/java/io/quarkus/vertx/http/deployment/EagerSecurityInterceptorCandidateBuildItem.java[`io.quarkus.vertx.http.deployment.EagerSecurityInterceptorCandidateBuildItem`, window="_blank"] :: +++Vert.X route handlers run before REST layer can't determine which endpoint is going to be invoked, what are endpoint annotations etc. Therefore, security setting that requires knowledge of invoked method (initial intention is to provide this with RESTEasy Reactive resources, however the principle is applicable to other stacks as well) and needs to be run prior to any security check should use this build item. The build item is only required for stacks that do not run security checks via CDI interceptors, as there, you can simply use interceptor with higher priority.+++
a|icon:lock[title=Fixed at build time] [[quarkus-core_quarkus.native.pie]]`link:#quarkus-core_quarkus.native.pie[quarkus.native.pie]`
68301
+
68302
+
68303
+
[.description]
68304
+
--
68305
+
Explicit configuration option to generate a native Position Independent Executable (PIE) for Linux. If the system supports PIE generation, the default behaviour is to disable it for link:https://www.redhat.com/en/blog/position-independent-executable-pie-performance[performance reasons]. However, some systems can only run position-independent executables, so this option enables the generation of such native executables.
a|icon:lock[title=Fixed at build time] [[quarkus-core_quarkus.native.remote-container-build]]`link:#quarkus-core_quarkus.native.remote-container-build[quarkus.native.remote-container-build]`
a|icon:lock[title=Fixed at build time] [[quarkus-core_quarkus.native.pie]]`link:#quarkus-core_quarkus.native.pie[quarkus.native.pie]`
1224
+
1225
+
1226
+
[.description]
1227
+
--
1228
+
Explicit configuration option to generate a native Position Independent Executable (PIE) for Linux. If the system supports PIE generation, the default behaviour is to disable it for link:https://www.redhat.com/en/blog/position-independent-executable-pie-performance[performance reasons]. However, some systems can only run position-independent executables, so this option enables the generation of such native executables.
a|icon:lock[title=Fixed at build time] [[quarkus-core_quarkus.native.remote-container-build]]`link:#quarkus-core_quarkus.native.remote-container-build[quarkus.native.remote-container-build]`
a|icon:lock[title=Fixed at build time] [[quarkus-native-pkg-native-config_quarkus.native.pie]]`link:#quarkus-native-pkg-native-config_quarkus.native.pie[quarkus.native.pie]`
288
+
289
+
290
+
[.description]
291
+
--
292
+
Explicit configuration option to generate a native Position Independent Executable (PIE) for Linux. If the system supports PIE generation, the default behaviour is to disable it for link:https://www.redhat.com/en/blog/position-independent-executable-pie-performance[performance reasons]. However, some systems can only run position-independent executables, so this option enables the generation of such native executables.
a|icon:lock[title=Fixed at build time] [[quarkus-native-pkg-native-config_quarkus.native.remote-container-build]]`link:#quarkus-native-pkg-native-config_quarkus.native.remote-container-build[quarkus.native.remote-container-build]`
Copy file name to clipboardExpand all lines: _versions/main/guides/ansible.adoc
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ include::_attributes.adoc[]
6
6
7
7
Let’s see how to build and deploy a Quarkus app using https://docs.ansible.com/ansible/latest/index.html[Ansible]. We’ll see how we can automate the entire process, from the code checkout to the application compilation using Maven and then its deployment and start of the service, as a https://systemd.io/[systemd service], on the target system using Ansible and its collection for Quarkus.
8
8
9
-
The first part, the application code checkout, compilation and packaging on the Ansible (where Ansible runs). We’ll use the getting-started sample application provided in its {quickstarts-tree-url}/getting-started[Quarkus QuickStarts directory] as a base for this tutorial. We’ll also leverage the https://galaxy.ansible.com/middleware_automation/quarkus[Quarkus collection] for Ansible, an extension for Ansible that alleviates the boilerplate required and to quickly build and deploy a Quarkus using Ansible.
9
+
The first part, the application code checkout, compilation and packaging on the Ansible (where Ansible runs). We’ll use the getting-started sample application provided in its link:{quickstarts-tree-url}/getting-started[Quarkus QuickStarts directory] as a base for this tutorial. We’ll also leverage the https://galaxy.ansible.com/middleware_automation/quarkus[Quarkus collection] for Ansible, an extension for Ansible that alleviates the boilerplate required and to quickly build and deploy a Quarkus using Ansible.
0 commit comments