Hi @srose
thanks for reporting this issue ;)
the complete realm export from keycloak has some other properties which if not defined in your configuration will still be used by kccli realm-Representation during a realm import.

I created a fix for your use case with the user by excluding the attribute from keycloak
it is worth noting that the issue might persist for other properties if not explicitly defined in your JSON import.

When applying a JSON or YAML configuration to Keycloak, a comparison is made between the realm defined in the Keycloak console and the configuration you are attempting to import. This process can lead to unintended updates due to additional configurations that Keycloak automatically includes during the import process.

For example, if you apply a simple and empty realm configuration like this:

{
  "realm": "simple"
}

At first glance, it may seem like you’ve only created an empty realm. However, if you export this same realm after the import, you’ll notice that Keycloak has added extra configurations beyond what you initially defined. These additional configurations are automatically provided by Keycloak and can cause unwanted or unnecessary updates during subsequent imports.

It’s important to understand that these changes are inherent to how Keycloak operates. While some of these attributes can be safely ignored, others may require proper handling or adjustments in your configuration to prevent issues. For example, certain scenarios can be addressed correctly or fixed, as demonstrated in specific cases like #883