fix: Ajust-OpenAPI-EdgeApp---type-weight-to-int #155
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update CreateOriginsRequest_addresses Schema
This Pull Request includes updates to the CreateOriginsRequest_addresses and OriginsResultResponse_addresses schemas in the edgeapplications.yaml file.
Changes:
Added is_active, weight, and server_role properties to the CreateOriginsRequest_addresses schema. These properties are necessary to align the request schema with the OriginsResultResponse_addresses schema.
Updated the weight property in the OriginsResultResponse_addresses schema from a string type to an integer type. This change aligns with the data type of the weight property in the CreateOriginsRequest_addresses schema.
Added format: int64 to the weight property in the CreateOriginsRequest_addresses schema. This specifies that the weight property should be a 64-bit integer.
These changes ensure consistency between the request and response schemas and provide clearer expectations for the API users about what data should be included in the request and what data they can expect in the response.