Adapt to changes for openEO API 1.1.0
Closed this issue · 1 comments
flahn commented
| Title | Adapt to changes for openEO API 1.1.0 |
|---|---|
| Date | 2021-11-11 |
| Issue | #93 |
| Category | Functionality |
| Description | The openeo package is designed to be flexible in terms of the version of the openEO API unless there are major changes on the endpoints. That means that the functions will continue to work with minor changes on the API, when the naming in STAC definitions or return objects changes. To keep up-to-date with the changes and the API versions we need to check the changes for potential conflicts with the implementation and make further adaptions. By adding more geo-spatial usability functions in the future the dependency on certain metadata fields will increase and this might cause an increase in future maintanenance. |
| Dependencies | OpenEO API Specification |
| Links | Changelog |
| Priority | High |
| Impact | Low |
| Effort | Medium |
Go through the changelog and make the client fully compliant to API version 1.1.0
flahn commented
To wrap this up, the check of API change log showed that the OIDC device code authentication flow and the settings for the default OIDC provider were the critical features to be implemented. Other changes were covered, because the meta data objects are accepted as send from the back-end. Users could already access new fields.