<settings>
    <profiles>
        <profile>
          <id>testprofile</id>
          <properties>
            <junit-version>4.13</junit-version>
            <compiler-version>3.7.0</compiler-version>
          </properties>
        </profile>
    </profiles>
    <activeProfiles>
        <activeProfile>testprofile</activeProfile>
    </activeProfiles>

     *
     * @param model The model into which to merge the values defined by the profile, must not be <code>null</code>.
     * @param profiles The (read-only) list of profiles whose values should be injected, must not be <code>null</code>.
     * @param request The model building request that holds further settings, must not be {@code null}.

				PodMaxBackoffSeconds:     ptr.To[int64](10),
				Profiles: []configv1.KubeSchedulerProfile{
					{
						SchedulerName: ptr.To("default-scheduler"),
						Plugins:       getDefaultPlugins(),
						PluginConfig:  pluginConfigs},
				},
			},
		},
		{
			name: "two profiles",
			config: &configv1.KubeSchedulerConfiguration{
				Parallelism: ptr.To[int32](16),
				Profiles: []configv1.KubeSchedulerProfile{
					{

 * specific language governing permissions and limitations
 * under the License.
 */
package org.apache.maven.profiles;

import java.util.List;
import java.util.Map;
import java.util.Properties;

import org.apache.maven.model.Profile;
import org.apache.maven.profiles.activation.ProfileActivationException;

/**
 * ProfileManager
 */
@Deprecated
public interface ProfileManager {

helm show values istio/istio-cni
```

### Profiles

Istio Helm charts have a concept of a `profile`, which is a bundled collection of value presets.
These can be set with `--set profile=<profile>`.
For example, the `demo` profile offers a preset configuration to try out Istio in a test environment, with additional features enabled and lowered resource requirements.

  <packaging>jar</packaging>

  <name>Maven Integration Test :: MNG-2309</name>
  <description>
    Test that profiles are injected in declaration order, with the last profile being the most dominant.
  </description>

  <profiles>
    <!-- NOTE: Using intentionally more than two profiles to prevent random test success -->
    <profile>
      <id>pom-a</id>
      <properties>
        <pomProperty>a</pomProperty>

  <artifactId>child</artifactId>
  <version>1.0-SNAPSHOT</version>

  <name>Maven Integration Test :: MNG-4034</name>
  <description>
    Verify that dependencies defined in profiles are subject to the dependency management of the parent.
  </description>

  <profiles>
    <profile>
      <id>maven-core-it</id>
      <activation>
        <activeByDefault>true</activeByDefault>
      </activation>
      <dependencies>

under the License.
-->

<project>
    <modelVersion>4.0.0</modelVersion>
    <artifactId>aid</artifactId>
    <groupId>gid</groupId>
    <version>0.1</version>
    <packaging>pom</packaging>

    <profiles>
        <profile>
            <id>+invalid-id</id>
        </profile>
        <profile>
            <id>-invalid-id</id>
        </profile>
        <profile>
            <id>!invalid-id</id>

		t.Fatal(err)
	}

	// multiple profiles config
	multiProfilesConfig := filepath.Join(tmpDir, "multi-profiles.yaml")
	if err := os.WriteFile(multiProfilesConfig, []byte(fmt.Sprintf(`
apiVersion: kubescheduler.config.k8s.io/v1
kind: KubeSchedulerConfiguration
clientConnection:
  kubeconfig: '%s'
profiles:
- schedulerName: "foo-profile"
  plugins:
    reserve:
      enabled:

}

tasks.bootRun {
    mainClass = 'com.example.demo.Demo'
    args '--spring.profiles.active=demo'
}
// end::accessors[]

// tag::lazy[]
tasks.named('bootJar') {
    archiveFileName = 'app.jar'
    mainClass = 'com.example.demo.Demo'
}

tasks.named('bootRun') {
    mainClass = 'com.example.demo.Demo'
    args '--spring.profiles.active=demo'
}