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.

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

feat: stencil #99

Merged
merged 3 commits into from
May 24, 2024
Merged

feat: stencil #99

merged 3 commits into from
May 24, 2024

Conversation

asms
Copy link
Contributor

@asms asms commented May 24, 2024

What this PR does / why we need it

The purpose of this PR is to be able to use this library for accessing the production Vault server. This can be seen in the second commit of this PR. This first commit is just an auxiliary restencil.

Re-stencil the repo to update to a newer version of Go which supports log/slog.

Update the interface of EnsureLoggedIn and IsLoggedIn to remove logrus, in favor of olog/slog, and to remove the dependency on box configs, which are specific to devenv.

@asms asms changed the title Asms/restencil feat: stencil May 24, 2024
@asms asms requested a review from a team May 24, 2024 06:16
// Uses a combination of built-in slog and olog functionality to
// provide a standard, structured logging interface and implementation.
// *slog.Logger instance are concurrency safe.
var log *slog.Logger = olog.New()

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Welcome to the dark side

@asms asms merged commit da6473b into main May 24, 2024
5 checks passed
@asms asms deleted the asms/restencil branch May 24, 2024 21:23
@getoutreach-ci-2
Copy link

🎉 This PR is included in version 1.15.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@malept
Copy link
Member

malept commented May 28, 2024

@asms @AndrewWinterman FYI, this is a breaking change which basically requires everything that depends on this library to be refactored in a non-trivial manner. This should have been a major version bump. Alternatively, there could have been a new function that uses log/slog instead of logrus for API compatibility purposes.

The release notes for 1.15.0 are also incomplete. If you're going to make a breaking API change, at minimum please update the release notes accordingly instead of making consumers read your PR to figure out what's going on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants