Repository navigation
v0.36.1
v0.36.1
The services
- A realm applied by a release before v0.35.0 carries on instead of failing. v0.35.0 moved the conformance client from a variable to a declaration without
movedblocks, so a development realm from an earlier release planned to re-create it and stopped on409 Client kanzo-conformance-api already exists.movedblocks take it to its new address (module.application["kanzo-conformance"],module.application_api["kanzo-conformance"]); where nothing was there they move nothing. auth-realmapplies the realm alone only when it is not there yet. The first, targeted apply (-target=keycloak_realm.kanzo) is what an empty Keycloak needs; on an existing realm it is skipped, since-targetexcludes the moved instances (Moved resource instances excluded by targeting).- An application that registered itself from a Terraform root of its own before v0.35.0 moves those resources into the realm's state once, with
terraform state mv, beforeauth-realmruns — keasy'srealm-migrate(keasyinfra/dev/platform.yaml) is the worked example.
No package changed: every @kanzo-tech/* is republished at 0.36.1 as it was in 0.36.0.