* the compile classpath and the runtime classpath, the version from the
     * runtime classpath is going to be used.
     *
     * In addition, the test runtime classpath is going to be configured to
     * be consistent with the main runtime classpath.
     *
     * Prefer {@link #useCompileClasspathVersions()} unless you have special
     * requirements at runtime.
     */

}
// end::declare-configuration[]

// tag::concrete-classpath[]
configurations {
    // declare a configuration that is going to resolve the compile classpath of the application
    compileClasspath.extendsFrom(someConfiguration)

    // declare a configuration that is going to resolve the runtime classpath of the application
    runtimeClasspath.extendsFrom(someConfiguration)
}
// end::concrete-classpath[]

}
// end::declare-configuration[]

// tag::concrete-classpath[]
configurations {
    // declare a configuration that is going to resolve the compile classpath of the application
    compileClasspath {
        extendsFrom(someConfiguration)
    }

    // declare a configuration that is going to resolve the runtime classpath of the application
    runtimeClasspath {
        extendsFrom(someConfiguration)
    }
}

	AlpnOverrideMetadataKey = "alpn_override"
)

// ALPNH2Only advertises that Proxy is going to use HTTP/2 when talking to the cluster.
var ALPNH2Only = pm.ALPNH2Only

// ALPNInMeshH2 advertises that Proxy is going to use HTTP/2 when talking to the in-mesh cluster.
// The custom "istio" value indicates in-mesh traffic and it's going to be used for routing decisions.

     * <p>
     * The job should not throw exceptions.
     * Any exceptions thrown are going to fail the build and may prevent the {@code buildFinished} callback from firing.
     * <p>
     * The build configuration inputs are not recorded for the job.
     * For example, changes to the environment variables read by the job are not going to invalidate the configuration cache.
     * The job is also allowed to freely start external processes.

 * @param <RESULT> the result of executing the rule, which may be the same as the DETAILS, but will often be
 * a different type that the caller can use to reproduce the execution of the rule. This object is the one
 * that is going to be cached, and most likely the thing the caller really cares about
 */
public interface CachingRuleExecutor<KEY, DETAILS, RESULT> {
    /**

        ModuleComponentRepository<?> sourceRepository = findSourceRepository(component.getSources());
        // First try to determine the artifacts locally before going remote
        sourceRepository.getLocalAccess().resolveArtifactsWithType(component, artifactType, result);
        if (!result.hasResult()) {

	"istio.io/istio/pkg/config/analysis/msg"
	"istio.io/istio/pkg/config/resource"
	"istio.io/istio/pkg/config/schema/gvk"
)

// ImageAutoAnalyzer reports an error if Pods and Deployments with `image: auto` are not going to be injected.
type ImageAutoAnalyzer struct{}

var _ analysis.Analyzer = &ImageAutoAnalyzer{}

const (
	istioProxyContainerName = "istio-proxy"
	manualInjectionImage    = "auto"
)

		valid.Netns,
	).Return(nil)

	dpServer := &meshDataplane{
		kubeClient: client.Kube(),
		netServer:  fs,
	}

	handlers := setupHandlers(ctx, client, dpServer, "istio-system")

	// We are not going to start the server, so the sockpath is irrelevant
	pluginServer := startCniPluginServer(ctx, "/tmp/test.sock", handlers, dpServer)

	// label the namespace

Unlike many projects on GitHub, the Go project does not use its bug tracker for general discussion or asking questions.
We only use our bug tracker for tracking bugs and tracking proposals going through the [Proposal Process](https://go.dev/s/proposal-process).

For asking questions, see:

* [The golang-nuts mailing list](https://groups.google.com/d/forum/golang-nuts)

* [The Go Forum](https://forum.golangbridge.org/), a web-based forum