-
Notifications
You must be signed in to change notification settings - Fork 71
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.
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
Regex support for --secret-type #287
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, however I'm really not comfortable with the fact that you changed the tests without any explanation. I want to be sure that this PR don't introduce any breaking change and those changes suggest that it does.
Hey, what should I follow-up on? |
Let's try to revive this PR. I repaired the read errors metric. |
Any updates on when this could be merged/released? |
Could we proceed forward with this change? Our team also eagers for this feature as it is impossible for us to rely on a static list of secret keys. |
Hi @Nuckal777, sorry for the delay. With the latest changes it looks good to me. If you can rebase the branch to resolve conflicts I will merge it. And it would be awesome if you could implement the idea described here also. |
242bdf0
to
cf57f31
Compare
Here you go. Because we have go1.23, we can avoid the callback stuff by using iterators. 🎉 |
🎉 This PR is included in version 3.18.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Hi,
this is an implementation for 242, because #243 seems a bit inactive. There are two notable changes: