exception.

If you're removing violations from the exception list, or if you have good
reasons to add new violations to this list, please update the file using:

 - `UPDATE_API_KNOWN_VIOLATIONS=true ./hack/update-codegen.sh`

It is up to API reviewers to review the list and make sure new APIs follow our API conventions.

**NOTE**: please don't hide changes to this file in a "generated changes" commit, treat it as
source code instead.

blank_issues_enabled: false
contact_links:
  - name: Security Contact
    about: Please report security vulnerabilities to ******@****.***
  - name: Question or Problem
    about: Ask a question or ask about a problem in GitHub Discussions.
    url: https://github.com/tiangolo/fastapi/discussions/categories/questions
  - name: Feature Request

the Gerrit change.

**Please ensure you adhere to every item in this list.**

More info can be found at https://github.com/golang/go/wiki/CommitMessage

+ The PR title is formatted as follows: `net/http: frob the quux before blarfing`
  + The package name goes before the colon
  + The part after the colon uses the verb tense + phrase that completes the blank in,
    "This change modifies Go to ___________"

 */

package org.gradle.api.artifacts;

import javax.annotation.Nullable;

/**
 * Contains and allows configuring component module metadata information.
 * For information and examples please see {@link org.gradle.api.artifacts.dsl.ComponentModuleMetadataHandler}
 *
 * @since 2.2
 */
public interface ComponentModuleMetadataDetails extends ComponentModuleMetadata {

    /**

Provide a reproducible test case that is the bare minimum necessary to generate
the problem. If possible, please share a link to or attach code demonstrating
the problem.

**Any other info / logs**
Include any logs or source code that would be helpful to diagnose the problem.
If including tracebacks, please include the full traceback. Large logs and files

apiVersion: release-notes/v2
kind: feature
area: security
releaseNotes:
- |
  **Updated** default value of the feature flag `VERIFY_CERT_AT_CLIENT` to true.
  This means server certificates will be automatically verified using the OS CA certificates when not using a DestinationRule caCertificates field.
  If undesired please use the new `compatibilityVersion` feature to fallback to old behavior, or `insecureSkipVerify`

For details, refer to the following guidelines.

## Key scripts

* [`verify-all.sh`](verify-all.sh): This script is a vestigial redirection, Please do not add "real" logic. It is equivalent to `make verify`.
* [`update-all.sh`](update-all.sh): This script is a vestigial redirection, Please do not add "real" logic. 
The `true` target of this makerule is `hack/make-rules/update.sh`.It is equivalent to `make update`.

## Attention

        echo "### NOT starting on installation, please execute the following statements to configure fess service to start automatically using chkconfig"
        echo " sudo chkconfig --add fess"
        echo "### You can start fess service by executing"
        echo " sudo service fess start"

    elif command -v update-rc.d >/dev/null; then

A. Please check `${KIBANA_HOME}/config/kibana.yml` and set correct Elasticsearch URL.

Example:
```
# The Elasticsearch instance to use for all your queries.
elasticsearch.url: "http://localhost:9201"
```

#### Q. I imported "fess\_log.ndjson" but no results found.

      uses: actions/stale@v8
      with:
        repo-token: ${{ secrets.GITHUB_TOKEN }}