[E2E Test] Add E2E test for using beacons and reactors
Open
Nobody has claimed this yet.
Tests
- Dominant language
- Python
- Stars
- 15.7k
- Forks
- 5.6k
- Avg merge
- 2d 44m
- Merged PRs (30d)
- 80
Description
Description
Add a E2E test for the documented example here: https://docs.saltproject.io/en/latest/topics/beacons/index.html#id2
To sum up the documentation for the tests:
- Create inotify beacon that monitors a file
- Create a reactor file that if that file is changed the Salt master will automatically return the contents back to the original content.
- Change the contents of the file
- Verify that the contents of the file get changed back to the original contents automatically.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the documented beacons example at https://docs.saltproject.io/en/latest/topics/beacons/index.html#id2 and identify the repository's E2E test entry point. Reproduce the inotify beacon and reactor flow described in the issue, then verify that changing the monitored file causes its contents to return to the original content automatically.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100