Skip to content

Releases: uptick/gitops

0.3.5

10 Jun 01:24

Choose a tag to compare

  • Fixed get_client function, which was breaking db.download-backup.

0.3.4

03 Jun 14:57

Choose a tag to compare

  • Updated newtenant commands to point to new cluster (these should all eventually be moved out of this repo anyway, as they don't make sense here..)

0.3.2

01 Jun 09:03

Choose a tag to compare

  • Fixed gitops db.copy-db command; added a check to ensure source and target clusters match.

0.3.1

26 May 12:37

Choose a tag to compare

Introduced multi-cluster support in the gitops client package

  • gitops summary now displays target cluster for each app.
  • target cluster is now considered as a tag in the context of filters and excludes.
  • running commands against apps now infers which cluster the commands should run on, going by the heuristic that the app's target cluster name is expected to match the kubeconfig context name.

0.2.11

13 May 13:22

Choose a tag to compare

  • Multi-cluster support -- a single app definitions repo can now manage apps across multiple clusters. An instance of Gitops server will need to run on each cluster.
  • AWS account_id is now stringformatted into the app image template.
  • Internal cleanups (mainly to gitops server).

0.2.9

22 Apr 04:17

Choose a tag to compare

Make summary avoid secrets, allowing use without decrypting repo.

0.2.8

17 Apr 05:21

Choose a tag to compare

Enables non-interactive mode for migration (and by extension command)

0.2.7

16 Apr 02:41

Choose a tag to compare

Adds a --no-interactive option to bump, allowing CI tools to bump without user input.
Allows sequential migration option.

0.2.6

16 Apr 02:02

Choose a tag to compare

Bump no longer requires secret files. These can remain encrypted and bumps can still be done.

Achieved by making secret loading optional on app loading.

0.2.5

24 Jan 00:10

Choose a tag to compare

  • Fixed output not displaying when running commands on a single server.
  • Hash colouring is now consistent between runs.
  • Default db instance bumped from t2 to t3.