Quentin Aubert

- update metadata from amdin screen "subscription" - update plan -> then subscriptions are synchronized in OtoroshiVerifierJob

In case of env mode, it could be nice to block aggregation between 2 environment if those 2 are not same. it's a security setup up just with env mode

Besides fixes #707 and #705, we use RuntimeException in other parts of Daikoku like the bug we fixed.

- [ ] in the UI we should be able to distinguish a child key - [ ] we should be enable/disable single child by remove/add authorized entities in oto

Like APi transfer ownership, in some case it could be nice to have the ability to transfer subscription to another team (ex: my team will be split into 2 teams)

modal settings for email step is not translated

related to "valid until" in Otoroshi, an API admin can setup a validity date. - [ ] this date can only been setup by API owner - [ ] subscriber...

Avoid user to go in team backoffice to get apikeys, just get its from UI/usage plans