// Module included in the following assemblies:
//
// * microshift_configuring/microshift-config-snippets.adoc

:_mod-docs-content-type: CONCEPT
[id="microshift-example-mixed-config-snippets_{context}"]
= Examples of mixed configuration snippets

[role="_abstract"]
When you use mixed configuration snippets in {product-title}, object fields merge and the last-read snippet replaces list values. File order controls which list entries apply.

In the following example, the values of both `advertiseAddress` and `auditLog.maxFileAge` fields merge into the configuration, but only the `c.com` and `d.com` `subjectAltNames` values are retained. This happens because the numbering in the filename indicates that the `c.com` and `d.com` values are higher priority.

.Example `10-advertiseAddress.yaml` snippet
[source,yaml]
----
apiServer:
  advertiseAddress: "microshift-example"
----

.Example `20-audit-log.yaml` snippet
[source,yaml]
----
apiServer:
  auditLog:
    maxFileAge: 12
----

.Example `30-SAN.yaml` snippet
[source,yaml]
----
apiServer:
  subjectAltNames:
    - a.com
    - b.com
----

.Example `40-SAN.yaml` snippet
[source,yaml]
----
apiServer:
  subjectAltNames:
    - c.com
    - d.com
----

.Example configuration result
[source,yaml]
----
apiServer:
  advertiseAddress: "microshift-example"
  auditLog:
    maxFileAge: 12
  subjectAltNames:
    - c.com
    - d.com
----
