github.com/gobuffalo/flect v0.2.0/go.mod h1:W3K3X9ksuZfir8f/LrfVtWmCDQFfayuylOJ7sz/Fj80=
github.com/gobwas/glob v0.2.3 h1:A4xDbljILXROh+kObIiy5kIaPYD8e96x1tgBhUI5J+Y=
github.com/gobwas/glob v0.2.3/go.mod h1:d3Ez4x06l9bZtSvzIay5+Yzi0fmZzPgnTbPcKjJAkT8=
github.com/gobwas/httphead v0.1.0/go.mod h1:O/RXo79gxV8G+RqlR/otEwx4Q36zl9rqC5u12GKvMCM=

        <![CDATA[
        The {@code <exclusion>} element contains information required to exclude
        an artifact to the project.
        <p>
        The {@code groupId} and {@code artifactId} fields are interpreted as glob patterns.

        @see java.nio.file.FileSystem#getPathMatcher
        ]]>
      </description>
      <fields>
        <field>
          <name>groupId</name>
          <version>4.0.0+</version>

forte.id

// Mozilla Corporation : https://mozilla.com
// Submitted by Ben Francis <******@****.***>
mozilla-iot.org

// Mozilla Foundation : https://mozilla.org/
// Submitted by glob <glob@mozilla.com>
bmoattachments.org

// MSK-IX : https://www.msk-ix.ru/
// Submitted by Khannanov Roman <******@****.***>
net.ru
org.ru
pp.ru

the Kubernetes API directly. To avoid this, the project attempts to minimize additions to the `values.yaml` API where possible. If the change is a dynamic runtime configuration, it probably belongs in the [MeshConfig API](https://github.com/istio/api/blob/master/mesh/v1alpha1/config.proto). This allows configuration without re-installing or restarting deployments. If the change is to a Kubernetes field (such as modifying a Deployment attribute), it will likely need to be install-time configuration....