Breaking (!) API changes for v2 API, March 28 to April 4
This week's changelog for the mittwald API includes the removal of the de.mittwald.v1.ingress.TargetDirectory schema from various request and response properties, the addition of new endpoints for changing extension contexts and removing extension logos, and the introduction of a non-success response status for ACME certificate issuance requests.
Summary
- The schema
de.mittwald.v1.ingress.TargetDirectoryhas been removed from theoneOflist in the request property for thePOSToperationingress-create-ingressat the path/v2/ingresses. This is a breaking change. - The schema
de.mittwald.v1.ingress.TargetDirectoryhas also been removed from theoneOflist in the request property for thePATCHoperationingress-update-ingress-pathsat the path/v2/ingresses/{ingressId}/paths. This is a breaking change. - Additionally, the schema
de.mittwald.v1.ingress.TargetDirectoryhas been removed from theoneOflist in the request property for thePUToperationdeprecated-ingress-pathsat the path/v2/ingresses/{ingressId}/paths. This is a breaking change. - The schema
de.mittwald.v1.ingress.TargetDirectoryhas been removed entirely from the API schema. - The schema
de.mittwald.v1.ingress.TargetDirectoryhas been removed from theoneOflist in the response property for thePOSToperationingress-list-ingresses-compatible-with-certificateat the path/v2/actions/list-ingresses-compatible-with-certificatefor the response status200. - The schema
de.mittwald.v1.ingress.TargetDirectoryhas been removed from theoneOflist in the response property for theGEToperationingress-list-ingressesat the path/v2/ingressesfor the response status200. - The schema
de.mittwald.v1.ingress.TargetDirectoryhas been removed from theoneOflist in the response property for theGEToperationingress-get-ingressat the path/v2/ingresses/{ingressId}for the response status200. - A non-success response with the status
412has been added for thePOSToperationingress-request-ingress-acme-certificate-issuanceat the path/v2/ingresses/{ingressId}/actions/request-acme-certificate-issuance. - A new endpoint has been added for the
PUToperationextension-change-contextat the path/v2/contributors/{contributorId}/extensions/{extensionId}/context. - A new endpoint has been added for the
DELETEoperationextension-remove-logoat the path/v2/contributors/{contributorId}/extensions/{extensionId}/logo. - The schema
de.mittwald.v1.ingress.TargetDirectoryhas been removed from theoneOflist in the response property for theGEToperationdeprecated-ingress-list-ingressesat the path/v2/projects/{projectId}/ingressesfor the response status200.
Disclaimer: This summary is AI-generated. If you find any discrepancies, please refer to the detailed changes below.
Detailed changes
Changes in "Create an Ingress"
- ⚠️ Breaking: removed '#/components/schemas/de.mittwald.v1.ingress.TargetDirectory' from the 'paths/items/target' request property 'oneOf' list
For details, refer to the POST/ endpoint.
Changes in "Update the paths of an Ingress"
- ⚠️ Breaking: removed '#/components/schemas/de.mittwald.v1.ingress.TargetDirectory' from the '/items/target' request property 'oneOf' list
For details, refer to the PATCH/ endpoint.
Changes in "Update an Ingresses paths"
- ⚠️ Breaking: removed '#/components/schemas/de.mittwald.v1.ingress.TargetDirectory' from the '/items/target' request property 'oneOf' list
For details, refer to the PUT/ endpoint.
Changes in ""
- removed the schema 'de.mittwald.v1.ingress.TargetDirectory'
For details, refer to the unknown operation endpoint.
Changes in "List Ingresses compatible with a certificate"
- removed '#/components/schemas/de.mittwald.v1.ingress.TargetDirectory' from the '/items/paths/items/target' response property 'oneOf' list for the response status '200'
For details, refer to the POST/ endpoint.
Changes in "Change the context of an Extension"
- endpoint added
For details, refer to the PUT/ endpoint.
Changes in "Remove the logo of an extension"
- endpoint added
For details, refer to the DELETE/ endpoint.
Changes in "List Ingresses"
- removed '#/components/schemas/de.mittwald.v1.ingress.TargetDirectory' from the '/items/paths/items/target' response property 'oneOf' list for the response status '200'
For details, refer to the GET/ endpoint.
Changes in "Get an Ingress"
- removed '#/components/schemas/de.mittwald.v1.ingress.TargetDirectory' from the 'paths/items/target' response property 'oneOf' list for the response status '200'
For details, refer to the GET/ endpoint.
Changes in "Request the ACME certificate issuance of an Ingress"
- added the non-success response with the status '412'
For details, refer to the POST/ endpoint.
Changes in "List Ingresses belonging to a project"
- removed '#/components/schemas/de.mittwald.v1.ingress.TargetDirectory' from the '/items/paths/items/target' response property 'oneOf' list for the response status '200'
For details, refer to the GET/ endpoint.
Client package releases
Release Summary: mittwald PHP SDK v2.1.126
The latest release of the mittwald PHP SDK, version v2.1.126, introduces significant changes by removing several classes and methods related to the customer agency verification feature. This update suggests a refactoring or a change in approach for handling agency verification within the API client.
Key Changes:
- Deleted Classes: Multiple classes associated with aborting, creating, and retrieving agency verifications have been removed.
- Interface Changes: Methods
abortAgencyVerification,createAgencyVerification, andgetOpenAgencyVerificationhave been removed from theCustomerClientinterface. - Implementation Changes: Related implementations in
CustomerClientImplhave been removed.
For more details, visit the release page.
Release v2.1.125 of Mittwald PHP SDK
The latest release of the Mittwald PHP SDK, v2.1.125, introduces several new features and improvements focused on agency verification processes and context manipulation.
Added Features
-
Abort Agency Verification: A new endpoint allows users to abort an open agency verification process, with various response types for different HTTP status codes, including successful and error responses.
-
Create Agency Verification: New classes have been added to handle the creation of agency verification requests, along with comprehensive error handling for different scenarios.
-
Get Open Agency Verification: An endpoint to retrieve the status of an agency verification request has been implemented, complete with detailed response classes for both successful and error outcomes.
Changes in Classes
-
The
TargetDirectoryclass has been refactored intoAbortAgencyVerificationOKResponseBodyandExtensionChangeContextOKResponseBodyto better handle specific responses. -
New functionality for
ExtensionChangeContexthas been introduced, including request handling and error response classes.
This release enhances the SDK's capabilities in managing agency verification and context changes, providing robust error handling and improved user interaction. For more details, visit the release page.
mittwald PHP SDK Release v2.1.124
The mittwald PHP SDK has released version v2.1.124. This release introduces enhancements and changes focused on improving request handling and error management.
New Features
- Ingress Request Handling Enhancements: The
DomainClientImplclass now supports handling the412 Precondition Failedresponse. This enhancement allows the API client to effectively manage scenarios where request preconditions are not met.
Changes
- A new class,
IngressRequestIngressAcmeCertificateIssuancePreconditionFailedResponse, has been introduced. This class encapsulates the structure of the412response, facilitating improved error handling and clearer response management. It includes methods for validation and JSON serialization.
mittwald JavaScript SDK Release 4.126.0
The mittwald JavaScript SDK has been updated to version 4.126.0. This release includes an update to the generated client, enhancing its functionality. For more details, you can view the release on GitHub here.
mittwald JavaScript SDK Release 4.125.0
The mittwald JavaScript SDK has been updated to version 4.125.0. This release includes an update to the generated client, enhancing the SDK's functionality. For more details, you can view the release on GitHub.