1.10.0

0.7.4

• Changed the branch naming convention so it will be consistent with the user/task name

1.9.0

1.9.0

• Added values schema for the helm chart

Bugfixes

• Long running tasks were not retried to monitor their status.
• When a task pod fails, it will be retried with a fresh request
• Fixed an issue with github delivery where the branch name relied on the user info. As a backup now, a timestamp will be used

1.8.0

1.8.0

• Added a controller.skipUserAuth field to skip keycloak authentication from a github user and its sync. Defaults to false so the existing behaviour is kept unless is desired.

  With this set to true you will truest that anything that argoCD detects on a git server, will be allowed to run.

  Another consequence, with skipUserAuth set to true the Analytics CRD will not have users as a required fields

1.7.0

• Fixed an issue with multiple link-user jobs can be created
• Optimized the github checkout to depth 1 for link-user jobs

1.6.0

0.7.4

• Changed the branch naming convention so it will be consistent with the user/task name

1.5.0

1.5.0

Bugfix

• Fixed an issue with link user jobs name which could have ended up with invalid characters

1.4.0

1.4.0

• Prefixed all of the cluster-wide resources with the helm release name, granting uniqueness.
• Parameterized CRD_GROUP and STORAGE_CLASS in the analytics-operator
• Moved the controller's specific ClusterRole and bindings into namespaced ones

1.3.0

1.3.0

Bugfix

• Fixed an issue that caused the controller to retry even when the review was pending

1.2.0

1.2.0

• Added a dynamic configuration to global.taskReview in the values files. This is only effective when deployed with the federated node. It will hold the result release until approved from the api, which in turns should set the task's CRD annotation approved to "true" and allowing result delivery. Defaults to false.

1.1.0

0.7.4

• Changed the branch naming convention so it will be consistent with the user/task name