-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Update depgaurd rules to prevent logrus from being imported in e #47962
Conversation
This pull request is automatically being deployed by Amplify Hosting (learn more). |
3ab89b3
to
8971f94
Compare
_ "github.com/aws/aws-sdk-go-v2/service/sts" | ||
_ "github.com/aws/aws-sdk-go-v2/service/sts/types" | ||
_ "github.com/beevik/etree" | ||
_ "github.com/cloudflare/cfssl/csr" |
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.
It looks like this slipped in for some license related tests. I'm working on removing and will follow up with another PR once it's no longer needed.
8971f94
to
43148e3
Compare
The teleport.e repo was recently converted to log exclusively with slog. In order to prevent logrus from accidentally being reintroduced into teleport.e the logrus depguard rule was updated to include the e repo. Additionally the e_imports.go file was updated to reflect that logrus is no longer required.
43148e3
to
60f2611
Compare
The teleport.e repo was recently converted to log exclusively with slog. In order to prevent logrus from accidentally being reintroduced into teleport.e the logrus depguard rule was updated to include the e repo. Additionally the e_imports.go file was updated to reflect that logrus is no longer required.