Skip to content

Releases: spacecloud-io/mission-control

v0.21.5

05 Sep 06:37
@YourTechBud YourTechBud
v0.21.5
719aeab
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.21.5 Latest
Latest

This is an incremental release where the following has been done:

  • Updated Mission Control theme to match the new SpaceCloud website theme.
  • Updated outdated libraries to the latest version
  • Fixed a bug in the DB read rest endpoint which didn't allow use of joins.
  • Improved test coverage for the database module.

Upgrade guide

Follow the steps to migrate from v0.20.0 and above:

  • Backup your current config using space-cli (space-cli --project <project_id> get all /path/to/backup/dir)
  • Backup setup configuration (space-cli inspect sc-setup-config.yaml)
  • Download the latest version of space-cli (Linux | Windows | Mac) and run space-cli update -f sc-setup-config.yaml.
  • Make sure you run Reload Schema in Database > Settings for each SQL database you've added in SpaceCloud.

Ping us on #general of our Discord server, if you face any issues while migrating.

Assets 2
Loading

v0.21.0

19 Feb 13:17
@YourTechBud YourTechBud
v0.21.0
daf811a
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.21.0

This is a minor release containing few enhancements and fixes.

Changes

  • Added support changing the request payload format in graphQL API #1526
  • Dataloader improvements #1487 #1501
  • Improved data type compatibility with all SQL databases #1496 #1424 #1465 #1467 #1469
  • Add support to display the raw SQL query being fired along with the time it took to get the result. #1120
  • Added a DockerCompose file for deploying SC with docker #1253

To see the complete list of enhancements/fixes, check out the v0.21.0 milestone.

Contributors

A special thanks to @narayandreamer for redesigning out website (link: https://spaceuptech.com)

Upgrade guide

Follow the steps to migrate from v0.20.0 and above:

  • Backup your current config using space-cli (space-cli --project <project_id> get all /path/to/backup/dir)
  • Backup setup configuration (space-cli inspect sc-setup-config.yaml)
  • Download the latest version of space-cli (Linux | Windows | Mac) and run space-cli update -f sc-setup-config.yaml.
  • Make sure you run Reload Schema in Database > Settings for each SQL database you've added in SpaceCloud.

Ping us on #general of our Discord server, if you face any issues while migrating.

Assets 2
Loading

v0.20.1

27 Dec 06:03
@YourTechBud YourTechBud
v0.20.1
79e0f7b
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.20.1

This is a minor release of Space Cloud that has a few improvements and bug fixes.

  • Added bit(1) support in MySQL and fixed runner related errors when using gateway standalone #1453
  • Optimized links to use native joins wherever possible #1422
  • Added support to aggregate fields of joint tables #1421

To see the complete list of enhancements/fixes, check out the v0.20.1 milestone.

Upgrade guide

Follow the steps to migrate from v0.20.0:

  • Backup your current config using space-cli (space-cli --project <project_id> get all /path/to/backup/dir)
  • Backup setup configuration (space-cli inspect sc-setup-config.yaml)
  • Download the latest version of space-cli (Linux | Windows | Mac) and run space-cli update -f sc-setup-config.yaml.

Ping us on #general of our Discord server, if you face any issues while migrating.

Assets 2
Loading

v0.20.0

05 Dec 08:46
@HeyItsJs HeyItsJs
v0.20.0
698ae51
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.20.0

This is a major release of Space Cloud that has tons of improvements and a few breaking changes.

Revamped eventing architecture

Space Cloud now uses a CDC (Change Data Capture) based eventing mechanism to capture database events reliably. Space Cloud uses Debezium and Redis under the hood to implement a reliable and performant eventing system.

Perks

  • Eventing works even for mutations made directly to the database from outside of Space Cloud.
  • All the previous limitations are gone. Events would be captured even if mutations are made without the primary key in the where clause or even if the primary key is not of type ID.
  • Stronger guarantees and reliability.

New data types

Thanks to the new eventing architecture, eventing is not tied to specific data types anymore. Hence, we have added a few data types that were asked for a lot of time:

  • Date
  • Time
  • Autoincrementing/Serial primary keys

More data types will be coming in the next releases.

Event-driven auto-scaling

We have added support for KEDA (Kubernetes Event-Driven Autoscaling) to Space Cloud. This means you can now autoscale your services based on:

  • Requests per second
  • Active requests
  • CPU consumption
  • Memory consumption
  • CRON schedule
  • Tons of other events (e.g. number of pending items in Kafka, SQL query output from Postgres, etc.), all thanks to KEDA!

Dropped Docker Support

As discussed and concluded in various community calls before, we have dropped the support for Docker as a target of the deployments module in Space Cloud. Space Cloud can now deploy services to Kubernetes only.

Dropping docker support would go a long way for us in developing and maintaining the deployments module. It would also help us to focus more on k8s and its ecosystem.

Other notable enhancements

  • Conditional event triggers #1392
  • Support for configuring underlying database driver #1023
  • Default limit clause in every ready query #1338
  • Support for specifying kid in JWT secrets #1405
  • Support for overriding token claims in event triggers #1389
  • Added support for search in all resources in Mission Control

To see the complete list of enhancements/fixes, check out the v0.20.0 milestone.

Upgrade guide

Follow the steps to migrate from the previous versions to v0.20.0:

  • Backup your current config using space-cli version 0.19.X. (space-cli --project <project_id> get all /path/to/backup/dir)
  • Delete the existing SC setup using kubectl delete -f https://raw.githubusercontent.com/spaceuptech/space-cloud/v0.19.7/install-manifests/kubernetes/local/space-cloud.yaml
  • Download the latest space-cli. (Linux | Windows | Darwin). This latest space-cli should be used from now for the further operations.
  • Make sure kubectl is pointing to the right k8s cluster and run space-cli setup.
  • Apply the backup config using space-cli apply /path/to/backup/dir

Ping us on #general of our Discord server, if you face any issues while migrating.

Assets 2
Loading

v0.19.7

09 Nov 15:10
@HeyItsJs HeyItsJs
v0.19.7
d5a1fc5
Compare
Choose a tag to compare
v0.19.7

This release contains a minor bugfix in ingress routes:

  • Gateway ended up following redirects from ingress routes #1394

Upgrade guide

Upgrade is possible from v0.17.0 and above.

Before upgrading your cluster, make sure you backup cluster config using space-cli --project <project_id> get all /path/to/backup/dir. If things go right, you'll be able to reapply all saved project config using space-cli apply /path/to/backup/dir.

For Docker-based deployments:

Simply run space-cli upgrade.

For Kubernetes based deployment:

We recommend setting up a fresh Kubernetes cluster and installing Istio and SC on top of it. Don't forget to backup all project config first!

Assets 2
Loading

v0.19.6

28 Oct 12:31
@HeyItsJs HeyItsJs
v0.19.6
5e52536
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.19.6

This release contains major performance optimisations and minor features

Enhancements

  • Native support for all types of SQL joins (LEFT, RIGHT, INNER, OUTER):
query {
  users (join: $join, where: $where) @db {
    name
    posts {
      title
      views {
        count
      }
    }
    address {
      pincode
      street
    }
  }
}

variables:

{
  "join": [
    {
      "type": "LEFT",
      "table": "posts",
      "on": {"users.id": "posts.user_id"},
      "join": [
        {
          "type": "LEFT",
          "table": "views",
          "on": {"posts.id": "views.post_id"}
        }
      ]
    },
    {
      "type": "LEFT",
      "table": "address",
      "on": {"users.id": "address.user_id"}
    }
  ]
}
  • Optimised (single SQL query) the same database joins when using the new join syntax #1135
  • New syntax for aggregations:
query {
  users (join: $join, where: $where) @db {
    name
    totalViews: views__count @aggregate(op: sum)
    maxViews: views__count @aggregate(op: max)
  }
}
  • Support for templating directive using JWT claims. #1370

Fixes

  • Fixed security rule editor crashing in Mission Control when the schema isn't provided #1369

Upgrade guide

Upgrade is possible from v0.17.0 and above.

Before upgrading your cluster, make sure you backup cluster config using space-cli --project <project_id> get all /path/to/backup/dir. If things go right, you'll be able to reapply all saved project config using space-cli apply /path/to/backup/dir.

For Docker-based deployments:

Simply run space-cli upgrade.

For Kubernetes based deployment:

We recommend setting up a fresh Kubernetes cluster and installing Istio and SC on top of it. Don't forget to backup all project config first!

Assets 2
Loading

v0.19.5

09 Oct 06:54
@HeyItsJs HeyItsJs
v0.19.5
677c771
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.19.5

This is a minor release containing few enhancements in ingress routing and a bug fix in letsencrypt module.

Enhancements

  • Added support for filtering ingress routes based on URL via Mission Control #1348
  • Show the number of ingress routes being displayed in the ingress routing page #1350
  • Add support for filtering ingress routes in space-cli get command #1349
  • Added a delay flag in space-cli apply command to slow down the rate at which the configs are applied #1351

Fixes

  • Fixed letsencrypt not working when email is configured #1347

Upgrade guide

Upgrade is possible from v0.17.0 and above.

Before upgrading your cluster, make sure you backup cluster config using space-cli --project <project_id> get all /path/to/backup/dir. If things go right, you'll be able to reapply all saved project config using space-cli apply /path/to/backup/dir.

For Docker-based deployments:

Simply run space-cli upgrade.

For Kubernetes based deployment:

We recommend setting up a fresh Kubernetes cluster and installing Istio and SC on top of it. Don't forget to backup all project config first!

Assets 2
Loading

v0.19.4

08 Oct 11:49
@HeyItsJs HeyItsJs
v0.19.4
fa8f311
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.19.4

This is a minor release containing few enhancements and fixes.

Enhancements

  • Added support for validating issuer and audience of JWT claim
  • Added support for specifying docker cmd in deployments via mission control
  • Added ability to provide the length of varchar in schema when using type ID
  • Added support to convert string to Object ID and vice versa

Fixes

  • Limited height of rows in the data browser table
  • Fixed limit clause not working if its value is provided through GraphQL variables

Upgrade guide

Upgrade is possible from v0.17.0 and above.

Before upgrading your cluster, make sure you backup cluster config using space-cli --project <project_id> get all /path/to/backup/dir. If things go right, you'll be able to reapply all saved project config using space-cli apply /path/to/backup/dir.

For Docker based deployments:

Simply run space-cli upgrade.

For Kubernetes based deployment:

We recommend setting up a fresh Kubernetes cluster and installing Istio and SC on top of it. Don't forget to backup all project config first!

Assets 2
Loading

v0.19.3

23 Sep 13:07
@HeyItsJs HeyItsJs
v0.19.3
968d609
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.19.3

This is a minor release containing few enhancements and fixes.

Enhancements

  • Added support for JWK URLs, thereby enabling integration with identity providers like Firebase Auth / Auth0 / Keycloak etc #1112
  • Added support for pod affinities #1274
  • Added support for adding labels to services deployed by Space Cloud #1282
  • Added support for multiples tasks and labels in deployments via Mission Control #753
  • Added support to dynamically encrypt, decrypt, hash and remove fields #1270
  • Added ability to forward the results of query and webhook rules to your service #1268
  • Added support for templating webhook requests #1267
  • Added support for optional timeouts in remote services config #1277
  • Added health check mechanism for integrations #1271
  • Added support for uploading an integration config directly from Mission Control #1272
  • Added logout button in Mission Control #1276
  • Added loading in Mission Control while generating RSA 256 secret #1263
  • Added support for space cli deploy --prepare command to work without a running SC cluster #1300
  • Added support for gcs setup on Kubernetes with space cloud secrets #1250
  • Added support for configuring default security rules while configuring file storage #1209
  • Added support of code splitting in Mission Control to reduce loading time #1278

Fixes

  • Fixed space api go delete file function deleting folders as well in local storage #1266
  • Fixed space api go not able to delete larger files to aws and gcp #1265
  • Fixed mission control resetting the security rules of remote endpoints when changing its type #1289
  • Fixed mission control not allowing to remove the last env pair while editing deployment #1292
  • Fixed mission control persisting file storage configuration form values after changing file store type #1262

Contributors

A special thanks to all our contributors for their help in this release!

Upgrade guide

Upgrade is possible from v0.17.0 and above.

Before upgrading your cluster, make sure you backup cluster config using space-cli --project <project_id> get all /path/to/backup/dir. If things go right, you'll be able to reapply all saved project config using space-cli apply /path/to/backup/dir.

For Docker based deployments:

Simply run space-cli upgrade.

For Kubernetes based deployment:

We recommend setting up a fresh Kubernetes cluster and installing Istio and SC on top of it. Don't forget to backup all project config first!

Assets 2
Loading

v0.19.2

02 Sep 05:56
@HeyItsJs HeyItsJs
v0.19.2
83d0e17
Compare
Choose a tag to compare
v0.19.2

This is a minor release containing few enhancements and fixes.

Enhancements

  • Add support for licensing logic to work in complete offline environments #1256
  • Added logging in space cloud #57
  • Added support for tracing requests in space cloud #462
  • Added flag to disable Mission Control in gateway #1196
  • Added flexibility to return status code for config mutation endpoints #1197

Fixes

  • Fixed space cloud not cleaning the temp files creating during multi-part file uploads in the filestore module #1245
  • Fixed copy/paste in the security rule builder not working on unsecured sites #1261
  • Unable to add HSA secret from Mission Control #1260
  • Prevent unnecessary fetching of latest version if a specific version is specified in the space-cli setup or upgrade command #1257

Contributors

A special thanks to all our contributors for their help in this release!

Upgrade guide

Upgrade is possible from v0.17.0 and above.

Before upgrading your cluster, make sure you backup cluster config using space-cli --project <project_id> get all /path/to/backup/dir. If things go right, you'll be able to reapply all saved project config using space-cli apply /path/to/backup/dir.

For Docker based deployments:

Simply run space-cli upgrade.

For Kubernetes based deployment:

We recommend setting up a fresh Kubernetes cluster and installing Istio and SC on top of it. Don't forget to backup all project config first!

Assets 2
Loading