Bumps [aiohttp](https://github.com/aio-libs/aiohttp) from 3.9.0 to 3.9.2. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/aio-libs/aiohttp/releases">aiohttp's releases</a>.</em></p> <blockquote> <h2>3.9.2</h2> <h2>Bug fixes</h2> <ul> <li> <p>Fixed server-side websocket connection leak.</p> <p><em>Related issues and pull requests on GitHub:</em> <a href="https://redirect.github.com/aio-libs/aiohttp/issues/7978">#7978</a>.</p> </li> <li> <p>Fixed <code>web.FileResponse</code> doing blocking I/O in the event loop.</p> <p><em>Related issues and pull requests on GitHub:</em> <a href="https://redirect.github.com/aio-libs/aiohttp/issues/8012">#8012</a>.</p> </li> <li> <p>Fixed double compress when compression enabled and compressed file exists in server file responses.</p> <p><em>Related issues and pull requests on GitHub:</em> <a href="https://redirect.github.com/aio-libs/aiohttp/issues/8014">#8014</a>.</p> </li> <li> <p>Added runtime type check for <code>ClientSession</code> <code>timeout</code> parameter.</p> <p><em>Related issues and pull requests on GitHub:</em> <a href="https://redirect.github.com/aio-libs/aiohttp/issues/8021">#8021</a>.</p> </li> <li> <p>Fixed an unhandled exception in the Python HTTP parser on header lines starting with a colon -- by :user:<code>pajod</code>.</p> <p>Invalid request lines with anything but a dot between the HTTP major and minor version are now rejected. Invalid header field names containing question mark or slash are now rejected. Such requests are incompatible with :rfc:<code>9110#section-5.6.2</code> and are not known to be of any legitimate use.</p> <p><em>Related issues and pull requests on GitHub:</em> <a href="https://redirect.github.com/aio-libs/aiohttp/issues/8074">#8074</a>.</p> </li> <li> <p>Improved validation of paths for static resources requests to the server -- by :user:<code>bdraco</code>.</p> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/aio-libs/aiohttp/blob/master/CHANGES.rst">aiohttp's changelog</a>.</em></p> <blockquote> <h1>3.9.2 (2024-01-28)</h1> <h2>Bug fixes</h2> <ul> <li> <p>Fixed server-side websocket connection leak.</p> <p><em>Related issues and pull requests on GitHub:</em> :issue:<code>7978</code>.</p> </li> <li> <p>Fixed <code>web.FileResponse</code> doing blocking I/O in the event loop.</p> <p><em>Related issues and pull requests on GitHub:</em> :issue:<code>8012</code>.</p> </li> <li> <p>Fixed double compress when compression enabled and compressed file exists in server file responses.</p> <p><em>Related issues and pull requests on GitHub:</em> :issue:<code>8014</code>.</p> </li> <li> <p>Added runtime type check for <code>ClientSession</code> <code>timeout</code> parameter.</p> <p><em>Related issues and pull requests on GitHub:</em> :issue:<code>8021</code>.</p> </li> <li> <p>Fixed an unhandled exception in the Python HTTP parser on header lines starting with a colon -- by :user:<code>pajod</code>.</p> <p>Invalid request lines with anything but a dot between the HTTP major and minor version are now rejected. Invalid header field names containing question mark or slash are now rejected. Such requests are incompatible with :rfc:<code>9110#section-5.6.2</code> and are not known to be of any legitimate use.</p> <p><em>Related issues and pull requests on GitHub:</em> :issue:<code>8074</code>.</p> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href=" |
||
|---|---|---|
| .. | ||
| main.py | ||
| README.md | ||
| requirements.txt | ||
Fake Data Generator Script
This script can be used to easily populate fake data into your local Grafana/OnCall setup. Currently the script is capable of generating the following objects:
- teams
- users
- schedules
- schedule on call shifts
Prerequisites
- Create/active a Python 3.11 virtual environment
pip install -r requirements.txt- Must have a local version of Grafana and OnCall up and running
- Generate an API key inside of Grafana OnCall
How to run
Note: The below flag values assume you are running a grafana container locally via the docker-compose setup.
The reason why there is a few separate steps involved is that we need to first create teams and users in the Grafana
instance. Later on, in order to create OnCall schedules/oncall-shifts, we need the OnCall user ID to do so. There is
currently no way to trigger a Grafana -> OnCall data sync via the public API, hence the manual step in the middle
to have data synced between Grafana and OnCall.
-
Create teams and users in Grafana. The
teamsandusersflags represent the number of teams and users you would like to create respectively:# by default this will generate 10 teams and 1000 users python main.py generate_teams_and_usersSee
python main.py generate_teams_and_users -hfor more information on how to run the command. -
Head to your OnCall setup, and trigger a Grafana -> OnCall data sync by visiting the plugin page.
-
Create schedules and on call shifts in OnCall. The
schedulesflag represents the number of OnCall schedules you would like to generate. Note that one on call shift is created for each schedule:# by default this will generate 100 schedules python main.py generate_schedules_and_oncall_shifts --oncall-api-token=<oncall-api-key>See
python main.py generate_schedules_and_oncall_shifts -hfor more information on how to run the command.