Updating an existing service
As your application evolves you will need to change its services and other components from time to time. This guide walks you through that process.
What you’ll need
Before you start, please check you have the following:
A Cloud 66 Account — If you don’t already have one sign up for a Cloud 66 account. There’s a free community plan and you’ll get full unlimited access to all products free for 14 days.
An existing application set up in Skycap — You can learn how to do that with our Getting started with Skycap guide.
An existing Formation defined in Skycap — You can learn how to do that with our Getting started with Skycap Formations guide.
In this example we’re using the same simple "hello world" project that we used in our Getting Started guides.
Updating your application code
In this example, you have decided to deploy a beta version of the Hello World application, and so you want to switch to using the “beta” branch of your application code. To do this:
Open your Cloud 66 dashboard and click on the name of the application you need to change.
Click on the edit icon in the top left-hand corner of the application detail panel to open the Service Editor
Change the Git Branch field from
betaand click Go
Once Skycap has confirmed access to the new code location, click Save changes
The changes you make here will not reflect in either your Formations or your Maestro deployments until you take a new Snapshot of the updated application.
Deploying your updated application
In order to see your beta version running, you first need to take a new Snapshot of your application. This will build your new code into a image so that you can deploy it to your cluster.
To do this:
- Click the Snapshot button and select Snapshot all
- Wait for the build to finish converting your code into images (or retagging existing images)
- Click on Formations in the right-hand panel
- Click on the “Hello World” Formation
- Click on the Render Formation button
You can now use the Cloud 66 Toolbelt to redeploy your application to Minikube following the same steps as in our Getting Started with Formations guide.
You’ll notice that the
cx command looks nearly identical to the one we used in our Formations guide, except that the UID of the
snapshot is different. This is because we are using our new snapshot with the new application code that we created in the previous step.
If you’ve followed all the steps successfully then the web page that loads when you run
minikube service command will have the word “(beta)” in the title.
- Learn how to add new services or components to a service.
- Learn how to roll back to an older version of your application using Snapshots.
- Learn how to add custom environment variables to your application.
- Learn how to set up access control and permissions on your Formations and Stencils
- Learn how to use your Habitus build flow within Skycap.
- Learn how to use validation policies to ensure your Stencils adhere to your standards and conventions.