-
Notifications
You must be signed in to change notification settings - Fork 407
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
Migrating traefik module #763
Conversation
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪 |
0281a16
to
a29bb61
Compare
Pinging @elastic/integrations (Team:Integrations) |
@@ -0,0 +1,23 @@ | |||
- name: traefik.health | |||
type: group | |||
release: ga |
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.
Hm... GA?
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.
I'm guessing you want me to change it to experimental
so it matches up with the release
in the package-level manifest.yml
?
BTW, this is what was generated by the migration script. Should we update it to generate release: experimental
?
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.
I guess it's because originally integrations were supposed to be 1:1 modules. If a module was released GA, so the integration too. You can open an issue, but I'm not sure about it's priority (rather low, it's easy to adjust after migration).
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.
I just realized that this release: ga
is in the fields.yml
, not the manifest.yml
. I'm fixing it to be release: experimental
but I'm seeing some other packages (e.g. nats
, docker
) where the release
is set to ga
in their fields.yml
but the package manifest.yml
has release: experimental
or release: beta
.
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.
Actually, I ended up just removing the release
field from this fields.yml
file (c857182). I checked the spec for field definition files and that field is not even mentioned in there. So I'm not even sure of it's purpose or if we need it. 🤷
|
||
## Compatibility | ||
|
||
The Traefik datasets were tested with Traefik 1.6. |
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.
I suppose that you didn't check compatibility with a more recent version?
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.
No, not yet. In this PR I'm just focussing on the basic migration. I will make a follow up PR to test with a more recent version and then make the necessary updates to the package.
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.
Ignore my previous comment. I updated the version of Traefik in this PR to 1.7.
There is a 2.x version series as well but I think we should leave that for a follow up PR as it might contain breaking changes. WDYT?
jenkins run the tests please |
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.
I think the only concern I have is to take a fresh screenshot. You can also put one in the issue description. @sorantis used to give suggestions what should be improved there.
44fed59
to
b43c460
Compare
10daba6
to
c2a87a3
Compare
* Migrating traefik module * Formatting package files * Removing invalid path field * Adding categories * Adding changelog file * Formatting tweaks * Adding pipeline test files * Adding YAML header * Adding system tests * Reformatting * Renaming pipeline test case files * Fixing pipeline tests * Adding ECS fields for health data stream * Adding README template file * Adding sample event for health data set * Adding system test for access data stream * Reformatting * Adding README * Removing host field from sample event files * Fixing kibana compatibility version * Testing with version 1.7 * Updating README * Remove release field from fields.yml * Remove temp field * Updating screenshot
What does this PR do?
Migrates the
traefik
module from Beats to Integrations.Checklist
changelog.yml
file.Screenshots
Related issues