-
**Problem description**
the "version" filed is not correct.
**Expected action**
fix it removing the release number
**Additional context**
as discussed for the CFS API here: https://github.c…
-
Many times, when you have to downgrade gloo, a user has to remove the CRDs (API contract) so that the downgraded new release will have the correct matching CRDs.
The approach was to delete the CRDs…
-
## Description
API versioning for portal related services
- administration
- notification
- apps
- services
- registration
**Why**
API versioning is planned to get implemented to enable a transparen…
-
We currently support 2 gov APIs.
- [ ] We will mark the old ("Classic") API as deprecated in 5.0, and remove it in 6.0.
- [ ] The new API takes a version-string, and we currently only have a preview…
-
-
## Short
The Oakestra APIs should have strong versioning to avoid unexpected breaking changes and easier extendability/modifiability.
## Proposal
Rather self-explanatory. We need to add/make sure…
-
Hey Jeremy,
This is more a question than a problem. I'm trying to implement api versioning based on path but then I need to change the lambda-api configuration to use the `base` property with v1, v…
-
Reported by @lingnoi:
## Description
Currently the communication between agent/cli and server is done using the API definition in **ankaios.proto**. The same is used for the communication throug…
-
Hello team,
I would like to check if all the [TypeSpec versioning decorators]https://typespec.io/docs/libraries/versioning/reference/decorators#@TypeSpec.Versioning.added), e.g. "@added", "@removed…
-
**Problem description**
Using Major Versions only in the API path is going to break ASPs when there's aggregation across CSP implementations (using different minor versions). i.e. minor versions are …