Slack Notifications (#958)
Slack notifications have arrived! You can set up the integration by navigating to Integrations > Slack, and clicking + Install Application. By default, these notifications will alert you when a new deployment of your application occurs, and will inform you if the deployment failed. This functionality will continue to be extended throughout the next release to notify on fatal application-level errors. Read the full documentation here.
Metrics Tab Updates and Autoscaling Visualization (#929)
We've added several new metrics graphs and features to make autoscaling thresholds more visible and to view how your application is autoscaling over time:
- If autoscaling is enabled, the CPU and memory usage graphs will now show how close your usage is to the threshold where autoscaling is triggered
- We've increased the granularity of the one hour view to 1 second, an improvement over the previous 15 seconds
- Metrics are now persistent, so that when a new version of the application is created, the old metrics will still be visible.
UI Improvements
We've modified our UI to show applications and jobs in a larger window, which will make them easier to navigate.
Source Visibility and Versioning (#929)
We've made several improvements that provide better visibility for seeing which Git commit (for those deploying from Github) or image tag (for those deploying from Docker) a certain revision of your application used. We've also added the ability to view which replicas are being added or terminated when a new version of your application is being deployed.
Template Upgrade Notes + Add-On Upgrades (#979)
Porter will now display upgrade notes when a new template upgrade is available, and it is now possible to upgrade add-ons that have been deployed through Porter!
CLI updates (#996)
We've made a few additions to the CLI!
porter run [application] -- [command]: this command will now create a new, ephemeral container that isn't serving production traffic, with the configuration copied from an existing pod. If you wish to connect to a running pod, use the--existing_podflag.porter logs [application]: this command will let you download logs from an existing pod, and optionally stream them with the-for--followflag.
We've also made the CLI much more usable for new users, and fixed several smaller issues: see other improvements.
Environment Groups can be Renamed (#891)
Thanks @anukul for the PR!
It is now possible to rename an environment group. To rename the group, click on the environment group in the Env groups tab, go to Settings, and enter a new name:
Github Actions Refactoring (#935)
Github actions files that get written to the Github repository are much simpler to read, and the steps are much easier to integrate into existing workflows. The action now calls a single step (after installing Porter) to deploy your application:
- name: Update Porter App
id: update_porter
timeout-minutes: 20
run: porter update --app from-gin
env:
PORTER_CLUSTER: <cluster-id>
PORTER_HOST: https://dashboard.getporter.dev
PORTER_PROJECT: <project-id>
PORTER_TOKEN: ${{ secrets.PORTER_TOKEN_<project-id> }}The command porter update --app [application] can also be called from your local computer with the flag --source github, which will perform the exact same action, so that you can trigger new deploys from your local workstation.
Contributing/Developing Updates
- We've added a frontend contributing guide that explains how to start working with the Porter frontend for contributing!
- We've added a section to the contributing guide that explains how to set up minikube for developing locally on MacOS
- We've added a frontend roadmap that shows how we're planning to refactor our frontend to be in line with best practices!