You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Encore has had built-in secrets management from day one, but it was quite limited: each secret value only applied to either {production} environments or to {development,preview,local} environments. This worked fine for basic use cases but was insufficient for many other use cases. For example, it's common to want a different secret value for local development specifically. In other use cases it was common to want to use the same secret value for all environments, which previously required setting the same value twice.
Today we're excited to announce a much more flexible secrets management experience that better addresses these use cases! Starting today, each secret value can be individually configured to apply to exactly the environment(s) you want.
For example:
# Set for local only
$ encore secret set --type local MySecret
# Set for all environments
$ encore secret set --type prod,dev,pr,local SomeOtherSecret
# Set for all preview environments and the environment named 'staging'
$ encore secret set --type pr --env staging SecretPassword
There's also a brand new secrets management UI on the Encore Platform:
Redacting sensitive data
Encore now supports redacting sensitive data from traces. Fields marked with the struct tag encore:"sensitive" (in request/response structs) are automatically redacted. This works for both individual values as well as nested fields.
Note that inputs to auth handlers are automatically marked as sensitive and are always redacted.
The encore.dev/storage/sqldb package now supports accessing the underlying connection pool using sqldb.Driver.
See the package documentation for more information.
We rely on the community to improve Encore, and we're always amazed by your incredible support and encouragement. A massive thank you to Patryk Siemiński, Mason Stewart, Sami Moustachir, Alex Yakubenko, Sean Knowles, David Mytton, Prasanna Balaji, Gabriel Bellon, and others for your contributions and feedback!
What’s next
We're very close to releasing support for metrics! We're also working on Kubernetes support, using existing infrastructure, and more.
– Remember to vote on your favorite feature on the roadmap!
As always, if you have questions or feedback, tell us on Slack or post on the Community Forum.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Introducing Secrets 2.0! 🎉
Encore has had built-in secrets management from day one, but it was quite limited: each secret value only applied to either
{production}
environments or to{development,preview,local}
environments. This worked fine for basic use cases but was insufficient for many other use cases. For example, it's common to want a different secret value for local development specifically. In other use cases it was common to want to use the same secret value for all environments, which previously required setting the same value twice.Today we're excited to announce a much more flexible secrets management experience that better addresses these use cases! Starting today, each secret value can be individually configured to apply to exactly the environment(s) you want.
For example:
Read the docs for more information.
There's also a brand new secrets management UI on the Encore Platform:
Redacting sensitive data
Encore now supports redacting sensitive data from traces. Fields marked with the struct tag
encore:"sensitive"
(in request/response structs) are automatically redacted. This works for both individual values as well as nested fields.Note that inputs to auth handlers are automatically marked as sensitive and are always redacted.
Read the docs for more information.
Database driver
The
encore.dev/storage/sqldb
package now supports accessing the underlying connection pool usingsqldb.Driver
.See the package documentation for more information.
Bugfixes and other improvements
Thanks to our contributors!
We rely on the community to improve Encore, and we're always amazed by your incredible support and encouragement. A massive thank you to Patryk Siemiński, Mason Stewart, Sami Moustachir, Alex Yakubenko, Sean Knowles, David Mytton, Prasanna Balaji, Gabriel Bellon, and others for your contributions and feedback!
What’s next
We're very close to releasing support for metrics! We're also working on Kubernetes support, using existing infrastructure, and more.
– Remember to vote on your favorite feature on the roadmap!
As always, if you have questions or feedback, tell us on Slack or post on the Community Forum.
We’re excited to hear your feedback! ❤️
Full Changelog: v1.12.1...v1.13.0
This discussion was created from the release Secrets 2.0.
Beta Was this translation helpful? Give feedback.
All reactions