Open source Firebase + Heroku to develop, scale and secure serverless apps on Kubernetes
This release contains major performance optimisations and minor features
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"}
}
]
}
query {
users (join: $join, where: $where) @db {
name
totalViews: views__count @aggregate(op: sum)
maxViews: views__count @aggregate(op: max)
}
}
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
.
Simply run space-cli upgrade
.
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!
This is a minor release containing few enhancements in ingress routing and a bug fix in letsencrypt module.
space-cli get
command #1349Upgrade 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
.
Simply run space-cli upgrade
.
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!
This is a minor release containing few enhancements and fixes.
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
.
Simply run space-cli upgrade
.
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!
This is a minor release containing few enhancements and fixes.
query
and webhook
rules to your service #1268space cli deploy --prepare
command to work without a running SC cluster #1300A special thanks to all our contributors for their help in this release!
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
.
Simply run space-cli upgrade
.
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!
This is a minor release containing few enhancements and fixes.
A special thanks to all our contributors for their help in this release!
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
.
Simply run space-cli upgrade
.
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!
This is a minor release containing the following enhancements:
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
.
Simply run space-cli upgrade
.
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!
We have finally released an enterprise-ready version of Space Cloud! 😀 It includes the following features:
Enterprise licenses for Space Cloud can be purchased from https://console.spaceuptech.com.
Drop us a mail at [email protected]
if you need any help for evaluating the enterprise version.
space-cli
and Mission Control as well. #1004Mission Control streaming service logs in realtime:
auth
claims are now available inside security rules of prepared queries. #1062count
function in aggregation works even without a selection set now. #1063Sample Queries
page in the database section. Added a play button to copy-paste the GraphQL queries to GraphiQL directly. #813destroy
command doesn't require root privileges while deleting services. #1015apply
command prints the id and spec when it encounters an error.setup
command giving error on windows./
inside the bucket. This was done in order to provide the same experience across all file storage providers. #1213result
field inside response body.These breaking changes are only applicable if you used either MySQL, GCS or Space Cloud's REST API for remote services. Join our discord channel if you need any help upgrading to v0.19.0
because of these breaking changes.
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
.
Simply run space-cli upgrade
.
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!
This is a minor release containing a single bug fix:
#1170 - Data race condition due to not acquiring a lock while reading the dataloader map.
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
.
Simply run space-cli upgrade
.
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!
This is a minor release containing improvements in security rules and ingress routing
Added support for accessing elements inside arrays in security rules. For example, the below security rule can now access the 3rd element inside tags
(array) :
{
"rule": "match",
"type": "string",
"eval": "==",
"f1": "args.doc.tags.2",
"f2": "mytag"
}
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
.
Simply run space-cli upgrade
.
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!
This is a patch release just containing a bug fix:
Setting the config of prepared queries wasn't working because of a recent optimization in v0.18.0
.
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
.
Simply run space-cli upgrade
.
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!