Describe the bug
When we hit the create config endpoint then along with the config ID we get the version id as well in the response body but we don't need to concern ourselves with that version ID since it is purely for db records and that version ID is not used anywhere or for any other endpoint, all we care about is the pair of config id and version number. Having version ID in create config's response body can be confusing to users.
Expected behavior
Version ID should be removed from the response body of create config endpoint, all it should have is config id, version number and the config blob we inserted along with any other supporting metadata, version ID not being one of them.
Describe the bug
When we hit the create config endpoint then along with the config ID we get the version id as well in the response body but we don't need to concern ourselves with that version ID since it is purely for db records and that version ID is not used anywhere or for any other endpoint, all we care about is the pair of config id and version number. Having version ID in create config's response body can be confusing to users.
Expected behavior
Version ID should be removed from the response body of create config endpoint, all it should have is config id, version number and the config blob we inserted along with any other supporting metadata, version ID not being one of them.