This topic describes how to update or archive releases.
You can deliver an update to an application after it has been released.
Note: Update checking defaults to every 15 minutes, but it can be configured by end customers.
To update a release:
From the Releases page in the Replicated vendor portal, click Create Release.
The YAML editor opens, and shows the contents of the most recently created release.
Edit the YAML files as needed.
Click Save Release.
From the Releases page, click Promote next to the newly created sequence.
Select the same channel again to promote this new release.
Any license installed from the selected channel will start with this new release, and any installation already running is prompted to update to the new release.
To install and test this new release in a test server, connect to the Replicated admin console dashboard on port :8800 using a web browser. At this point, it will likely show that our test application is "Up To Date" and that "No Updates Are Available". The admin console checks for new updates about every five hours, but you can force it to check now.
To check for updates now, go to the Application tab or Version History tab, and click "Check For Updates. On the Version History page, you see that the Deploy button is enabled. Additionally, it should say how many files were changed and how many lines are different. You can click on that to view the changes in the YAML file.
Click Deploy to apply the new YAML files. This should only take a few seconds to deploy.
You can archive releases to remove them from view on the Releases page.
Archiving a release that has been promoted does not remove the release from the channel's Release History page or prevent the app manager from downloading the archived release.
To archive one or more releases:
- From the Releases page, click the trash can icon in the upper right corner.
- Select one or more releases.
- Click Archive Releases.
- Confirm the archive action when prompted. Alternatively, click Cancel to cancel the archiving action.