This is because it is expected that **your users** would define the actual **URL path** where they want to receive the webhook request in some other way (e.g. a web dashboard).

### Check the docs { #check-the-docs }

Now you can start your app and go to [http://127.0.0.1:8000/docs](http://127.0.0.1:8000/docs).

You will see your docs have the normal *path operations* and now also some **webhooks**:

import org.gradle.api.tasks.InputFiles;
import org.gradle.api.tasks.TaskAction;

import java.net.URI;
import java.util.Map;
import java.util.stream.Collectors;
import javax.inject.Inject;

/**
 * Performs additional checks on changelog files, beyond whether they conform to the schema.
 */
public class ValidateChangelogEntryTask extends DefaultTask {
    private final ConfigurableFileCollection changelogs;

# Properties used to build to the RPM package
#

# Environment file
packaging.env.file=/etc/sysconfig/fess

# Default configuration directory and file to use in bin/plugin script

# Simple marker to check that properties are correctly overridden
packaging.type=rpm

# Custom header for package scripts
packaging.scripts.header=

                }),
        (accum, t) -> {
          /*
           * We assign these to variables before calling checkNotNull to work around a bug in our
           * nullness checker.
           */
          K key = keyFunction.apply(t);
          V newValue = valueFunction.apply(t);
          accum.put(
              checkNotNull(key, "Null key for input %s", t),

      }
    }

    /*
     * TODO(cpovirk): `return (V) removedValue` once our checker permits that.
     *
     * (We promoted a class of warnings into errors because sometimes they indicate real problems.
     * But now we need to "undo" some instance of spurious errors, as discussed in
     * https://github.com/jspecify/checker-framework/issues/8.)
     */
    return removedValue == null ? null : (V) removedValue;
  }

                }),
        (accum, t) -> {
          /*
           * We assign these to variables before calling checkNotNull to work around a bug in our
           * nullness checker.
           */
          K key = keyFunction.apply(t);
          V newValue = valueFunction.apply(t);
          accum.put(
              checkNotNull(key, "Null key for input %s", t),

    init {
        project.gradle.sharedServices.registerIfAbsent(NullawayStatusService.SERVICE_NAME, NullawayStatusService::class)
        group = LifecycleBasePlugin.BUILD_GROUP
        description = "Checks status of NullAway support in this project. Call unqualified to get summary for all projects."
    }

    @TaskAction
    fun action() {

## Project structure

Mostly a standard Maven project structure. The entry point `settings.kts` defines the TeamCity project.

There are 3 subprojects in the TeamCity project hierarchy: `Check` for Gradle builds, `Promotion` for releasing Gradle versions, `Util` for miscellaneous utilities.

## Develop and verify

    /**
     * Gets the flags of this DCERPC message
     * @return the message flags
     */
    public int getFlags() {
        return flags;
    }

    /**
     * Check if a specific flag is set.
     * @param flag the flag to check
     * @return whether flag is set
     */
    public boolean isFlagSet(final int flag) {
        return (this.flags & flag) == flag;
    }

    /**
     * Remove flag
     *

        printStream.accept("");
        // we have no DI here (to discover)
        printStream.accept("Goals:");
        printStream.accept("  help  - display this help message");
        printStream.accept("  check - check for available upgrades");
        printStream.accept("  apply - apply available upgrades");
        printStream.accept("");
        printStream.accept("Options:");