|
| 1 | +--- |
| 2 | +title: Release Notes |
| 3 | +permalink: /cloud/release-notes/12-2021 |
| 4 | +category: Release Notes |
| 5 | +menuOrder: 1 |
| 6 | +--- |
| 7 | + |
| 8 | +Following Cube Cloud becoming generally available in October 2021, we've been |
| 9 | +hard at work making improvements across the board. Let's have a quick run |
| 10 | +through them: |
| 11 | + |
| 12 | +## Database Connections |
| 13 | + |
| 14 | +Cube Cloud now supports configuring your own specified SSL certificates when |
| 15 | +connecting to databases. When creating a new deployment, check the 'SSL' box, |
| 16 | +and paste the relevant SSL certificates: |
| 17 | + |
| 18 | + |
| 19 | + |
| 20 | +## Git integration |
| 21 | + |
| 22 | +We've made it really easy to quickly add more Git branches to your Cube Cloud |
| 23 | +deployment and switch between them, just click the branch name in the status |
| 24 | +bar: |
| 25 | + |
| 26 | + |
| 27 | + |
| 28 | +Speaking of Git branches, you can now easily add and remove branches with the |
| 29 | +same switcher; click 'Add Branch' and enter a name for the new branch in the |
| 30 | +popup: |
| 31 | + |
| 32 | + |
| 33 | + |
| 34 | +These branches are shared; meaning everyone on your Cube Cloud team can see and |
| 35 | +edit them. This makes them super useful for out-of-band experiments where you |
| 36 | +can quickly test things in Cube Cloud without having to go through a CI/CD |
| 37 | +process. |
| 38 | + |
| 39 | +To round things off, you can also delete unused branches too; first make sure |
| 40 | +you are already on the branch, then open the switcher and click 'Remove Branch': |
| 41 | + |
| 42 | + |
| 43 | + |
| 44 | +## GitHub integration |
| 45 | + |
| 46 | +When connecting your GitHub repo to Cube Cloud, you can now choose a default |
| 47 | +branch for deployments: |
| 48 | + |
| 49 | + |
| 50 | + |
| 51 | +## Developer Mode |
| 52 | + |
| 53 | +We've seen a round of improvements to the Cube Cloud Developer Mode experience. |
| 54 | +When you're in Developer Mode, the status bar is now purple so you always know |
| 55 | +when it's active: |
| 56 | + |
| 57 | + |
| 58 | + |
| 59 | +If you've been editing a schema and navigate away, we warn you if there are any |
| 60 | +unsaved changes: |
| 61 | + |
| 62 | + |
| 63 | + |
| 64 | +And last but not least, we've added a new 'Generate Schema' button to the Schema |
| 65 | +page. Clicking this will let you re-generate schemas from your source database, |
| 66 | +or alternatively add rollups to existing schemas: |
| 67 | + |
| 68 | + |
| 69 | + |
| 70 | +## Query Tracing |
| 71 | + |
| 72 | +When inspecting queries in the Queries tab, you can now also see whether or not |
| 73 | +the query used a pre-aggregation: |
| 74 | + |
| 75 | + |
| 76 | + |
| 77 | +If you click a query from the list, we now provide more relevant information, |
| 78 | +like if the query built a pre-aggregation or not: |
| 79 | + |
| 80 | + |
| 81 | + |
| 82 | +## SQL API |
| 83 | + |
| 84 | +Following the release of the SQL API in Cube, we're happy to announce that you |
| 85 | +can also use it in Cube Cloud. You can enable it by clicking 'Deploy SQL API' |
| 86 | +from the Overview page, then click the 'How to connect your BI tool'. You should |
| 87 | +then see something similar to the following: |
| 88 | + |
| 89 | + |
| 90 | + |
| 91 | +You can read more about the Cube SQL API |
| 92 | +[in the documentation](https://cube.dev/docs/backend/sql), and we even have |
| 93 | +[a recipe that shows you how to connect the SQL API to Apache Superset](https://cube.dev/docs/recipes/using-apache-superset-with-cube-sql). |
| 94 | + |
| 95 | +## GraphQL API |
| 96 | + |
| 97 | +In parallel to the SQL API, we also are excited to announce a new GraphQL API. |
| 98 | +You can copy its’ URL from the Overview page, just under the SQL API: |
| 99 | + |
| 100 | + |
| 101 | + |
| 102 | +More information can be found |
| 103 | +[in the documentation](https://cube.dev/docs/backend/graphql); we hope you enjoy |
| 104 | +using it as much as we are 🤓 |
| 105 | + |
| 106 | +## Other Notable Improvements |
| 107 | + |
| 108 | +- When a deployment is connected to a Git monorepo, only commits to the Cube |
| 109 | + project folder will trigger a rebuild on Cube Cloud. |
| 110 | +- When switching from `stable` track to `latest`, Cube Cloud will now |
| 111 | + automatically restart the deployment. |
| 112 | +- `COMPILE_CONTEXT` now works correctly in Developer Mode. |
| 113 | +- Automatically switch to Developer Mode after adding a rollup using the Rollup Designer. |
| 114 | + |
| 115 | +That's all for this release, stay tuned for the release notes next time 😀 |
0 commit comments