Václav Muzikář
Václav Muzikář
I don't like mixing the schemes (i.e. `/admin/api/realms///clients//*`) either. What if we decoupled the realms from the version like this: `/admin/api/clients///*`. I.e. having the realm represented only as a path...
> as there should be a hierarchy of these resources I guess I was trying to say that this ^^ kinda contradicts the request for having distinct versions of the...
To summarize an offline discussion. We agreed on the following two alternatives: 1. `/admin/api////*` * E.g. `GET /admin/api/clients/v2/my-realm/clients/my-client-id` 2. `/admin/api///realms//*` * E.g. `GET /admin/api/clients/v2/realms/my-realm/clients/my-client-id` Option 1 doesn't leave our door...
> * Prominantly warn that usage of these endpoints is only for dev / ad hoc scenarios - otherwise users could consider any default version change breaking. > * Document...
> Makes it simpler to switch version as you only need to make the changes not change the path. In case we needed to bump the API version, it means...
@shawkins Virtual hosts for realm identification is definitely something we should look into in the future but I don't see it as something we need to figure out now, it's...
Do we really want to get rid of the concept of `latest`? I know it hasn't been maintained for some time but IMHO it still made sense. E.g. the Cloud...
@mposolda That is not ideal (the need to wait with merging until release). My concern would be that it's a manual process (which might be prone to errors – merging...
#14811 is still a breaking change, despite H2 not being a prod grade DB, some folks might be using it.