You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
There is no place to validate that serviceId conforms to the requested format.
Describe the solution you'd like
Provide a REST API on the API Gateway. This API should live under /conformance/validate and be available under the POST method. The API will accept the serviceId parameter. It will return the information on whether this serviceId is valid under the conformance criteria.
Acceptance Criteria
The logic will be merged into the v2.x.x branch
The /conformance/validate API won't require authentication
The /conformance/validate API will accept serviceId as a parameter
The /conformance/validate API returns 200 for serviceId that is only a lower case, doesn't contain symbols, and less than 64 characters
The /conformance/validate API returns 400 when there is an upper case letter
The /conformance/validate API return 400 when there is a symbol
The /conformance/validate API return 400 when it is longer than 64 characters. 64 characters are ok. 65 are not.
The video demo shows the functionality
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
There is no place to validate that serviceId conforms to the requested format.
Describe the solution you'd like
Provide a REST API on the API Gateway. This API should live under /conformance/validate and be available under the POST method. The API will accept the serviceId parameter. It will return the information on whether this serviceId is valid under the conformance criteria.
Acceptance Criteria
The text was updated successfully, but these errors were encountered: