Release v0.6.0

Environment Group Merging/Previews (#856)

Environment variables used to be overwritten when loading them from an environment group, and users were not notified of conflicting environment variables that may be superseded. Now, users will be notified of overrides. Thanks @Xetera for the PR!

Github App Migration (#895)

As announced in the previous release, we have now fully migrated to using a Github App instead of an OAuth apps for repository integrations. This will give us more opportunities for integrations and make the integration more stable. In addition, if you're working on Porter in a team and have your personal repositories linked up, other members of the team will not be able to see or interact with those repositories -- team members will only see the repositories that they have access to. To set up the Github App integration, click on the user icon in the top right of the platform, and click "Account Settings":

Webhook Regeneration (#916)

When a cluster is linked and unlinked on Porter, you may lose access to Porter webhooks that were written for a specific cluster, application, and namespace combination. If a webhook is not found for an application, we've now added the ability to recreate this webhook for a new cluster.

Other Improvements

• Fix bug where env file upload does not work for deleted keys (#877) -- thanks @anukul for the PR!
• Fix email verification for local instances on Porter (#914)
• Auto-send email verification emails on signup (#913)
• Better loading screen when metrics are returned as empty (#882)
• Fix pod selection to prevent first pod from being auto selected (#889)
• Fix environment variables for multi-line vars (#890)
• Improve load time performance after clicking into an application (#894)
• Show all objects when listing manifests in the "Manifests" tab (#896)
• Fix --port flag for the porter server start command (#915)
• Fix --path flag when calling porter update... commands (#906)

Release v0.5.0

Team Management and Access Control

Porter now supports different roles for collaborators within a Porter project. At the moment, the three supported roles are admin, developer, and viewer, with more granular access control coming soon! See the full documentation for more details.

CLI-Based Deployments and Upgrades

Creating a new application on Porter is now as simple as porter create web --app web-app! While the dashboard should still be the primary method for deploying applications, the CLI can now be used for upgrading and deploying applications. Read the full documentation here. Demo video.

Detailed Cluster Dashboard

Porter now displays a full cluster dashboard that shows all of the machines running your applications, along with detailed information about usage on each machine:

Transitioning to Github Apps

Starting on July 23rd (v0.6.0 release), Porter will be using a Github App to access your repositories, instead of an OAuth App (what's the difference?). All applications deployed via the OAuth app will continue to work, but new deployments must use the Github App. See this guide for setting up the Github App in your account. The Github App will provide the following benefits:

• Much simpler to control access to repositories: for example, excluding personal repositories from being listed, allowing access to specific organization repositories, etc.
• More resilient to a Github user revoking personal access tokens
• Tighter integrations: ability for the Github App to act as it's own user when creating commits, comment on PRs, and generate Github environments.

URLs for Resources

Most pages on Porter that display applications, jobs, and clusters now have shareable URLs, so that you can directly link to a specific resource when sharing an application with your team members.

New Add-Ons

We're excited to announce new add-ons for Tailscale, Wallarm, and Datadog!

• Datadog is a monitoring service that aggregates metrics from your applications, servers, and infrastructure.
• Tailscale is a VPN that creates a secure network between your servers. See our doc for deploying Tailscale on Porter, or read our blog post to learn more about Tailscale on Kubernetes. Deploying Tailscale on Porter gives you easy, secure access to your non-exposed applications and databases:
• Wallarm is a platform that lets you protect and monitor your APIs. See our doc for deploying Wallarm on Porter.

Other Improvements

• Live-update an opened application when re-deployed from a different process (other browser, webhook, etc)
• Fix a bug where Github login was failing due to strict cookie settings
• Load image tags properly from private Docker Hub images, and create valid credentials for pulling private Docker Hub images
• Fix a dashboard bug where system logs are rendered together with application logs

Release v0.4.4

Merge pull request #852 from porter-dev/0.5.0-job-status-endpoint

[0.5.0] Add job status endpoint

Release v0.4.3

Merge pull request #815 from porter-dev/lost-tailscale-changes

Service list form component for tailscale add-on

Release v0.4.2

Merge pull request #813 from porter-dev/0.4.2-cli-login-set-project

[0.4.2] Use the `config.Token` to set project after `porter auth login --token ...`

Release v0.4.1

• Fix issue where ECR image tags do not load properly in version 0.4.0 (#797)

Release v0.4.0

More detailed release notes soon to come

• Support deployments from the CLI (https://docs.getporter.dev/docs/deploying-from-the-cli)
• Cluster dashboard with view of nodes, namespace editor, and credential rotation

Release v0.3.4

Support deletion of specific job runs from the dashboard, along with minor fixes for frontend form.yaml styling.

Release v0.3.3

Merge pull request #758 from porter-dev/0.3.3-fix-restricted-domain

[0.3.3] Fix google restricted domain

Release v0.3.2

Adds support for proper URL-based routing