Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Explain plugin changes in a blog post #2093

Closed
carolynvs opened this issue May 23, 2022 · 0 comments · Fixed by #2121
Closed

Explain plugin changes in a blog post #2093

carolynvs opened this issue May 23, 2022 · 0 comments · Fixed by #2121
Assignees
@VinozzZ
Labels
docs Markdown ahoy! Updates needed on porter.sh or in dev docs.
Milestone
1.0

Comments

@carolynvs
Copy link
Member

The recent changes to the plugin protocol require uses to change their configuration. Let's explain in a blog post a few things:

  1. The plugins protocol has changed. We now persist sensitive data generated by Porter in a secret store.
  2. Let people know that they need to update their config file to pick a secrets plugin.
  3. List which plugins are suitable for production use.
@carolynvs carolynvs added this to the 1.0 milestone May 23, 2022
@carolynvs carolynvs added the docs Markdown ahoy! Updates needed on porter.sh or in dev docs. label May 23, 2022
@carolynvs carolynvs mentioned this issue May 23, 2022
Merged
4 tasks
@carolynvs carolynvs assigned carolynvs and VinozzZ and unassigned carolynvs May 26, 2022
@VinozzZ VinozzZ mentioned this issue May 31, 2022
Merged
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@VinozzZ VinozzZ

Labels
docs Markdown ahoy! Updates needed on porter.sh or in dev docs.
Projects
None yet
Milestone
1.0
Development

Successfully merging a pull request may close this issue.

add blog post for the new secret plugin protocol VinozzZ/porter
2 participants
@carolynvs @VinozzZ