Skip to content

v1.0.0-alpha.20

Pre-release
Pre-release
Compare
Choose a tag to compare
@getporterbot getporterbot released this 31 May 14:33
· 1038 commits to main since this release
v1.0.0-alpha.20
539645a
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Breaking Changes

🚨 The plugin protocol has changed in this release of Porter. You must use the most recent version of any plugins with porter v1.0.0-alpha.20 and higher.

The installation schema has changed. Data created with previous versions of Porter will not work with this release. We will start providing migrations from v0.38.* when we hit v1.0.0-beta.1.

Overview

This was a big release! Most of the changes in this release were driven by one feature: Store sensitive data generated by Porter in an external secret store instead of in Porter's database. Previously, if a bundle generated a sensitive output, it was stored in Porter's database in plain text. Now if Porter needs to persist sensitive data, we save it back to your configured secret store. This required a change to the secret plugin protocol, which is why all the plugins have been updated.

A few supporting features also went into this release to improve our ability to debug and troubleshoot plugins:

  • Distributed tracing support. We can now trace a porter command into the plugins that were called.
  • Changed the plugin protocol from net/rpc to gRPC.
  • Do not leak plugin connections when the user cancels a porter command. Porter now gracefully handles CTRL+C.

Features

Fixes

Misc

Contributors

carolynvs, joshuabezaleel, and 5 other contributors
Assets 22
Loading