-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Updated dev guide instructions to work with master #30014
Updated dev guide instructions to work with master #30014
Conversation
filebeat fails (hangs) on 8.0 due to `Elasticsearch is too old.` so updating to 8.1 as well as fixing up expectations around authentication and ssl.
This pull request does not have a backport label. Could you fix it @matschaffer? 🙏
NOTE: |
Pinging @elastic/obs-docs (Team:Docs) |
💚 Build Succeeded
Expand to view the summary
Build stats
❕ Flaky test reportNo test was executed to be analysed. 🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
Today I also found out that I could use Might be good to update this to include something like that. Additionally I'd like to link the modules dev doc to https://www.elastic.co/guide/en/beats/devguide/current/beats-contributing.html#running-testsuite somehow. Today the "Testing guide" link just points to a stub page. The way I found the module dev guide was through searching Elastic internal slack history for other people learning how to run filebeat system tests. |
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.
👍
@@ -485,8 +485,10 @@ run. | |||
In order to test the filesets with the sample logs and/or generate the expected output one should run the tests | |||
locally for a specific module, using the following procedure under Filebeat directory: | |||
|
|||
. Run an Elasticsearch instance locally using docker: `docker run -p 9200:9200 -p 9300:9300 -e "discovery.type=single-node" docker.elastic.co/elasticsearch/elasticsearch:8.0.0-SNAPSHOT` | |||
. Run an Elasticsearch instance locally using docker: `docker run --rm --name elasticsearch -p 9200:9200 -p 9300:9300 -e "ELASTIC_PASSWORD=changeme" -e "discovery.type=single-node" -e "xpack.security.http.ssl.enabled=false" docker.elastic.co/elasticsearch/elasticsearch:8.1.0-SNAPSHOT` |
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 idea of using 8.0.0-SNAPSHOT
was to use the snapshot from master. Do you know if there is now any other snapshot following master? Otherwise we may need to update this on every minor release 🤔
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 like master-SNAPSHOT
works. Presumably this will switch to main-SNAPSHOT
at some point but we can update when that happens and it should only happen once.
@@ -485,8 +485,10 @@ run. | |||
In order to test the filesets with the sample logs and/or generate the expected output one should run the tests | |||
locally for a specific module, using the following procedure under Filebeat directory: | |||
|
|||
. Run an Elasticsearch instance locally using docker: `docker run -p 9200:9200 -p 9300:9300 -e "discovery.type=single-node" docker.elastic.co/elasticsearch/elasticsearch:8.0.0-SNAPSHOT` | |||
. Run an Elasticsearch instance locally using docker: `docker run --rm --name elasticsearch -p 9200:9200 -p 9300:9300 -e "ELASTIC_PASSWORD=changeme" -e "discovery.type=single-node" -e "xpack.security.http.ssl.enabled=false" docker.elastic.co/elasticsearch/elasticsearch:8.1.0-SNAPSHOT` | |||
. Create an "admin" user on that Elasticsearch instance: `curl -u elastic:changeme http://localhost:9200/_security/user/admin -X POST -H 'Content-Type: application/json' -d '{"password": "changeme", "roles": ["superuser"]}'` |
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.
Would these changes be also needed when running tests in CI? Let's see if this PR passes 🤔 #30012
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.
You can also run these tests via mage pythonIntegTest TESTING_FILEBEAT_MODULES=elasticsearch
which launches a number of docker-compose services and I suspect is where the admin user gets created and that CI is doing something similar.
That flow takes a very long time (15min) and has some local failures, so wasn't practical for module development.
Pinging @elastic/integrations (Team:Integrations) |
@elastic/obs-docs any idea why this fails? IntelliJ is able to resolve the What I'm trying to fix is how https://www.elastic.co/guide/en/beats/devguide/current/beats-contributing.html#running-testsuite links to https://www.elastic.co/guide/en/beats/devguide/current/testing.html (part of the packetbeat guide) rather than https://github.com/elastic/beats/blob/8bdc6d2d38c8762582dd27be66dc3053b5e61346/docs/devguide/testing.asciidoc |
Ahhh. I think I got it. I opened elastic/docs#2364 to avoid the stumbling block I hit. Also I think we need to add @elastic/obs-docs as a writer to https://github.com/elastic/docs - I can't add it as a PR review target which means it lacks repo permissions. |
filebeat fails (hangs) on 8.0 due to `Elasticsearch is too old.` so updating to 8.1 as well as fixing up expectations around authentication, ssl, and information about options and where to find logs. (cherry picked from commit 3ed5763)
filebeat fails (hangs) on 8.0 due to `Elasticsearch is too old.` so updating to 8.1 as well as fixing up expectations around authentication, ssl, and information about options and where to find logs. (cherry picked from commit 3ed5763) Co-authored-by: Mat Schaffer <mat@elastic.co>
filebeat fails (hangs) on 8.0 due to
Elasticsearch is too old.
so updating to 8.1 as well as fixing up expectations around authentication and ssl.I've also included a little extra information about how to run the tests, look for logs, and some options (including one that will be added by #30103)
Rel: #29880