Hono: Align Tenant management API implementation with the spec

[dejanb]

At the moment Tenant management API specification defines that payload (without any mandatory parameters) is required during tenant creation. The implementation at the moment accepts empty body and adds 'enabled' field in that case. Empty body is also used in getting started examples.

We need to align specification with the implementation and examples.

[sophokles73]

FMPOV there is no need to supply and data in a request payload if I want to use the defaults. SO I would say that the spec should be relaxed accordingly.

[sophokles73]

@calohmn @ctron WDYT?

[calohmn]

I also think that we can change the spec to make the request body optional.

[dejanb]

I agree as well.

One question that I have is that with this change and changes in the #1711, should we bump the spec version?

[sophokles73]

One question that I have is that with this change and changes in the #1711, should we bump the spec version?

I think we should. Remember that this is public API and we need to apply semantic versioning.
The change introduced in #1711 seems to only be concerning the wording being changed from should not be included to must not be included and the change in this PR also looks backward compatible to me. So I would suggest to bump to 1.0.1. WDYT? @dejanb @ctron @calohmn

[sophokles73]

@dejanb can this be closed?

[sophokles73]

@dejanb can this be closed?