-
Notifications
You must be signed in to change notification settings - Fork 4
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
[DEVOPS-646] Refactor all output into plugins similar to Fact & Analyse #68
Conversation
52b7b3d
to
32cf1d5
Compare
87fe4b3
to
60c024a
Compare
Even though the env vars were being set in an earlier command, they were not being used in `go build`. Moving them to the actual command is what works.
@@ -0,0 +1,141 @@ | |||
package lagoon |
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.
Hmmm — this is a difficult choice, I like how we have the output package. It clearly illustrates what is an output plugin. However, problems being specific to Lagoon pose a bit of an issue with the convention.
We can leave it here for now, but I'm wondering if we want to make it part of the output package for consistency.
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 might make more sense in the future when actually implementing the plugin system - see the sample here: #69
Also added
lagoon-source
flag when pushing Problems to Insights.This PR introduces the interface & plugin system for Output, similar to how Fact & Analyse plugins are done.
Two new such interfaces are introduced:
Stdout
&Lagoon