chart: {{ template "minio.chart" . }} release: {{ .Release.Name }} heritage: {{ .Release.Service }} spec: podSelector: matchLabels: app: {{ template "minio.name" . }} release: {{ .Release.Name }} ingress: - ports: - port: {{ .Values.service.port }} - port: {{ .Values.consoleService.port }} {{- if not .Values.networkPolicy.allowExternal }} from: - podSelector: matchLabels: {{ template "minio.name" . }}-client: "true" {{- end }} {{- end }} minio/templates/poddisruptionbudget.yaml {{- if .Values.podD...

chart: {{ template "minio.chart" . }} release: {{ .Release.Name }} heritage: {{ .Release.Service }} spec: podSelector: matchLabels: app: {{ template "minio.name" . }} release: {{ .Release.Name }} ingress: - ports: - port: {{ .Values.service.port }} - port: {{ .Values.consoleService.port }} {{- if not .Values.networkPolicy.allowExternal }} from: - podSelector: matchLabels: {{ template "minio.name" . }}-client: "true" {{- end }} {{- end }} minio/templates/poddisruptionbudget.yaml {{- if .Values.podD...

chart: {{ template "minio.chart" . }} release: {{ .Release.Name }} heritage: {{ .Release.Service }} spec: podSelector: matchLabels: app: {{ template "minio.name" . }} release: {{ .Release.Name }} ingress: - ports: - port: {{ .Values.service.port }} - port: {{ .Values.consoleService.port }} {{- if not .Values.networkPolicy.allowExternal }} from: - podSelector: matchLabels: {{ template "minio.name" . }}-client: "true" {{- end }} {{- end }} minio/templates/poddisruptionbudget.yaml {{- if .Values.podD...

## Documenting webhooks with **FastAPI** and OpenAPI { #documenting-webhooks-with-fastapi-and-openapi }

With **FastAPI**, using OpenAPI, you can define the names of these webhooks, the types of HTTP operations that your app can send (e.g. `POST`, `PUT`, etc.) and the request **bodies** that your app would send.

            throwValidationErrorApi(messages -> messages.addErrorsCrudCouldNotFindCrudTable(GLOBAL, id));
            return null;
        })).status(Status.OK).result());
    }

    // POST /api/admin/fileauth/setting
    /**
     * Creates a new file authentication setting.
     * Validates that the associated file config ID is valid before creation.
     *

				<%-- Message --%>
				<div>
					<la:info id="msg" message="false">
						<div class="alert alert-info">${msg}</div>
					</la:info>
					<la:errors />
				</div>
				<la:form styleId="newPassword" method="post">
					<div class="input-group mb-3">
						<c:set var="ph_new_password">
							<la:message key="labels.login.placeholder_new_password" />
						</c:set>
						<la:password property="password" class="form-control"

The user of your API (an external developer) will create an invoice in your API with a POST request.

Then your API will (let's imagine):

* Send the invoice to some customer of the external developer.
* Collect the money.
* Send a notification back to the API user (the external developer).
    * This will be done by sending a POST request (from *your API*) to some *external API* provided by that external developer (this is the "callback").

     * @param body the request body containing stemmer override item information
     * @return JSON response with result status
     */
    // POST /api/admin/dict/stemmerOverride/setting/{dictId}
    @Execute
    public JsonResponse<ApiResult> post$setting(final String dictId, final CreateBody body) {
        body.dictId = dictId;
        validateApi(body, messages -> {});
        body.crudMode = CrudMode.CREATE;

            // END SNIPPET: clean
        }

        @Override
        public Collection<Alias> aliases() {
            return List.of(alias("pre-clean", BEFORE + Phase.CLEAN), alias("post-clean", AFTER + Phase.CLEAN));
        }
    }

    static class DefaultLifecycle implements Lifecycle {
        @Override
        public String id() {
            return Lifecycle.DEFAULT;
        }

				</p>
				<%-- Message --%>
				<div>
					<la:info id="msg" message="false">
						<div class="alert alert-info">${msg}</div>
					</la:info>
					<la:errors />
				</div>
				<la:form styleId="login" method="post">
					<div class="input-group mb-3">
						<c:set var="ph_username">
							<la:message key="labels.login.placeholder_username" />
						</c:set>
						<la:text property="username" styleId="username"