Releases: kabanero-io/kabanero-command-line-services
0.6.0-rc.1
New Stack hub architecture and multi-version support.
0.5.0
0.5.0-rc1
0.5.0-rc.1
Just publishing to be picked up by operator
0.4.0
0.4.0-rc.1
Changes in this release:
Detect if Git hub authorization is not configured and return http code 539 to Kabanero CLI if it is not
0.3.0
Changes:
global: Sorted Output
LIST
•Both active and Inactive Kabanero Collections will be listed
•New additions to the curated collection will be listed
SYNC
•Any collection that is in the curated collections will have desiredState set to active ( collections controller will set status to active ) if it is inactive in Kabanero
•Any collection that has been removed from the curated collections will have desiredState set to inactive ( collections controller will set status to inactive )
•New additions to the curated collection will be created as new Kabanero collection objects
Additional Function
•RETRY logic to access curated collection on GIT hub
•Liveness probe to detect if GIT connection is in failed state and recycle the Pod
0.3.0-rc.3
Changes:
global: Sorted Output
LIST
•Both active and Inactive Kabanero Collections will be listed
•New additions to the curated collection will be listed
SYNC
•Any collection that is in the curated collections will have desiredState set to active ( collections controller will set status to active ) if it is inactive in Kabanero
•Any collection that has been removed from the curated collections will have desiredState set to inactive ( collections controller will set status to inactive )
•New additions to the curated collection will be created as new Kabanero collection objects
Additional Function
•RETRY logic to access curated collection on GIT hub
•Liveness probe to detect if GIT connection is in failed state and recycle the Pod
0.3.0-rc.2
Changes:
global: Sorted Output
- LIST
•Both active and Inactive Kabanero Collections will be listed
•New additions to the curated collection will be listed - SYNC
•Any collection that is in the curated collections will have desiredState set to active ( collections controller will set status to active ) if it is inactive in Kabanero
•Any collection that has been removed from the curated collections will have desiredState set to inactive ( collections controller will set status to inactive )
•New additions to the curated collection will be created as new Kabanero collection objects - Additional Function
•RETRY logic to access curated collection on GIT hub
•Liveness probe to detect if GIT connection is in failed state and recycle the Pod
0.3.0-alpha.1
0.3.0-alpha.1 Kab CLI Service