centralcloud/oncall-engine
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
oncall-engine/engine/requirements.in

67 lines
1.8 KiB
Text
Raw Normal View History

Use pip-tools to handle Python deps (#3892) [pip-tools](https://github.com/jazzband/pip-tools) helps making builds deterministic, controlling deps (and indirect deps) upgrades (and versions consistency) avoiding unexpected (and potentially breaking) changes. We keep our direct deps in `requirements.in` from which we generate the `requirements.txt` (where *all* deps are pinned). We also constrain dev (and enterprise) deps based on base requirements. Check how to [update deps](https://github.com/jazzband/pip-tools?tab=readme-ov-file#updating-requirements).
2024-02-20 14:44:15 -03:00
babel==2.12.1
beautifulsoup4==4.12.2
celery[redis]==5.3.1
cryptography==38.0.4 # version 39.0.0 introduced an issue - https://stackoverflow.com/a/75053968/3902555
Bump django from 4.2.10 to 4.2.11 in /engine (#4079) Bumps [django](https://github.com/django/django) from 4.2.10 to 4.2.11. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/django/django/commit/61a986f53d805e4d359ab61af60a2dcd55befe25"><code>61a986f</code></a> [4.2.x] Bumped version for 4.2.11 release.</li> <li><a href="https://github.com/django/django/commit/3c9a2771cc80821e041b16eb36c1c37af5349d4a"><code>3c9a277</code></a> [4.2.x] Fixed CVE-2024-27351 -- Prevented potential ReDoS in Truncator.words().</li> <li><a href="https://github.com/django/django/commit/79739511397367c56d20393b93c5edd35f5cca53"><code>7973951</code></a> [4.2.x] Added release date for 4.2.11 and 3.2.25.</li> <li><a href="https://github.com/django/django/commit/86d8034972db5014769cdd4832125067f31b3e8b"><code>86d8034</code></a> [4.2.x] Refs <a href="https://redirect.github.com/django/django/issues/34900">#34900</a>, Refs <a href="https://redirect.github.com/django/django/issues/34118">#34118</a> -- Updated assertion in test_skip_class_unle...</li> <li><a href="https://github.com/django/django/commit/cb173bb088e32df3d9ee8bee3c579d88ea713e8f"><code>cb173bb</code></a> [4.2.x] Fixed <a href="https://redirect.github.com/django/django/issues/35172">#35172</a> -- Fixed intcomma for string floats.</li> <li><a href="https://github.com/django/django/commit/227ef29cff8ded8187c48b0aa955264cf83a01a4"><code>227ef29</code></a> [4.2.x] Added CVE-2024-24680 to security archive.</li> <li><a href="https://github.com/django/django/commit/e2f1907642c311b21d45d85a0aca7d9c05ede5cd"><code>e2f1907</code></a> [4.2.x] Post release version bump.</li> <li>See full diff in <a href="https://github.com/django/django/compare/4.2.10...4.2.11">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=django&package-manager=pip&previous-version=4.2.10&new-version=4.2.11)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/grafana/oncall/network/alerts). </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Joey Orlando <joey.orlando@grafana.com>
2024-03-19 21:14:44 +00:00
django==4.2.11
Use pip-tools to handle Python deps (#3892) [pip-tools](https://github.com/jazzband/pip-tools) helps making builds deterministic, controlling deps (and indirect deps) upgrades (and versions consistency) avoiding unexpected (and potentially breaking) changes. We keep our direct deps in `requirements.in` from which we generate the `requirements.txt` (where *all* deps are pinned). We also constrain dev (and enterprise) deps based on base requirements. Check how to [update deps](https://github.com/jazzband/pip-tools?tab=readme-ov-file#updating-requirements).
2024-02-20 14:44:15 -03:00
django-add-default-value==0.10.0
django-amazon-ses==4.0.1
django-anymail==8.6
django-cors-headers==3.7.0
# pyroscope-io==0.8.1
django-dbconn-retry==0.1.7
django-debug-toolbar==4.1
django-deprecate-fields==0.1.1
django-filter==2.4.0
django-ipware==4.0.2
django-log-request-id==1.6.0
django-migration-linter==4.1.0
django-mirage-field==1.3.0
django-mysql==4.6.0
django-polymorphic==3.1.0
django-ratelimit==2.0.0
django-redis==5.4.0
django-rest-polymorphic==0.1.10
django-silk==5.0.3
django-sns-view==0.1.2
djangorestframework==3.14.0
factory-boy<3.0
drf-spectacular==0.26.5
emoji==2.4.0
Use local arm64 grpcio wheel to make local builds on arm64 faster (#4000) This is the workaround to make local image build faster on arm64 machines This commit can be reverted once https://github.com/grpc/grpc/issues/34998 is resolved
2024-03-05 14:31:58 +08:00
# If the version of grpcio is changed
# upload a new arm64 wheel instead of /engine/grpcio-1.57.0-cp311-cp311-linux_aarch64.whl
Use pip-tools to handle Python deps (#3892) [pip-tools](https://github.com/jazzband/pip-tools) helps making builds deterministic, controlling deps (and indirect deps) upgrades (and versions consistency) avoiding unexpected (and potentially breaking) changes. We keep our direct deps in `requirements.in` from which we generate the `requirements.txt` (where *all* deps are pinned). We also constrain dev (and enterprise) deps based on base requirements. Check how to [update deps](https://github.com/jazzband/pip-tools?tab=readme-ov-file#updating-requirements).
2024-02-20 14:44:15 -03:00
grpcio==1.57.0
fcm-django @ https://github.com/grafana/fcm-django/archive/refs/tags/v1.0.12r1.tar.gz#sha256=7ec7cd9d353fc9edf19a4acd4fa14090a31d83d02ac986c5e5e081dea29f564f
hiredis==2.2.3
humanize==0.5.1
icalendar==5.0.10
lxml==4.9.2
markdown2==2.4.10
Add trace_id to log lines (#3982) # What this PR does This PR set up tracing to propagates trace_id to log lines. There are two different tracers: local one in manage.py - it's used when app is started via manage.py runserver. In this case spans will be just written in console. Second traces is confugured in wsgi.py. It will be used when app is runned via uwsgi and it will export traces via grpc. Feature is hidden behind the feature flag.
2024-03-04 14:42:43 +08:00
opentelemetry-sdk==1.23.0
opentelemetry-api==1.23.0
Use pip-tools to handle Python deps (#3892) [pip-tools](https://github.com/jazzband/pip-tools) helps making builds deterministic, controlling deps (and indirect deps) upgrades (and versions consistency) avoiding unexpected (and potentially breaking) changes. We keep our direct deps in `requirements.in` from which we generate the `requirements.txt` (where *all* deps are pinned). We also constrain dev (and enterprise) deps based on base requirements. Check how to [update deps](https://github.com/jazzband/pip-tools?tab=readme-ov-file#updating-requirements).
2024-02-20 14:44:15 -03:00
opentelemetry-exporter-otlp-proto-grpc==1.15.0
Add trace_id to log lines (#3982) # What this PR does This PR set up tracing to propagates trace_id to log lines. There are two different tracers: local one in manage.py - it's used when app is started via manage.py runserver. In this case spans will be just written in console. Second traces is confugured in wsgi.py. It will be used when app is runned via uwsgi and it will export traces via grpc. Feature is hidden behind the feature flag.
2024-03-04 14:42:43 +08:00
opentelemetry-instrumentation-logging==0.44b0
Use uwsgi instrumentation and log request headers (#3997) # What this PR does Use uwsgi instead of TracingMiddleware to not to mess up with span attrs. Also it's an attempt to fix different trace IDs between cortex-gw, oncall and labels plugin. Last, but not least - add a middleware to log request headers if OTEL is enabled. It's needed to debug tracing headers
2024-03-04 17:25:39 +08:00
opentelemetry-instrumentation-wsgi==0.44b0
Instrument requests lib (#4008) # What this PR does Instument requests lib to provide consistent trace_id
2024-03-05 13:22:34 +08:00
opentelemetry-instrumentation-requests==0.44b0
opentelemetry-instrumentation-django==0.44b0
Use pip-tools to handle Python deps (#3892) [pip-tools](https://github.com/jazzband/pip-tools) helps making builds deterministic, controlling deps (and indirect deps) upgrades (and versions consistency) avoiding unexpected (and potentially breaking) changes. We keep our direct deps in `requirements.in` from which we generate the `requirements.txt` (where *all* deps are pinned). We also constrain dev (and enterprise) deps based on base requirements. Check how to [update deps](https://github.com/jazzband/pip-tools?tab=readme-ov-file#updating-requirements).
2024-02-20 14:44:15 -03:00
phonenumbers==8.10.0
prometheus_client==0.16.0
psutil==5.9.4
psycopg2==2.9.3
pymdown-extensions==10.0
PyMySQL==1.1.0
python-telegram-bot==13.13
recurring-ical-events==2.1.0
redis==5.0.1
regex==2021.11.2
requests==2.31.0
slack-export-viewer==1.1.4
slack_sdk==3.21.3
social-auth-app-django==5.3.0
twilio~=6.37.0
urllib3==1.26.18
uwsgi==2.0.21
whitenoise==5.3.0
Google OAuth2 flow + fetch Google Calendar OOO events (#4067) # What this PR does The following is deployed under a feature flag. **How it works** 1. The user clicks on the "Connect using your Google account" button in the user profile settings modal 2. The UI makes a call to `GET /api/internal/v1/login/google-oauth2`. The backend has now been configured to add `apps.social_auth.backends.GoogleOAuth2` as a "`social_auth` backend". 3. The backend will respond w/ a URL which points to the Google OAuth2 consent screen. The frontend then proceeds by sending the user to this page. This URL includes the following query parameters (amongst others): - `redirect_uri` - this will send the user back to `/api/internal/v1/complete/google-oauth2` (ie. make another API call to the OnCall backend to finalize the Google OAuth2 flow) - `state` - this represents an `apps.auth_token.models.GoogleOAuth2Token` token. This allows us to identify the OnCall user once they've linked their Google account. 4. Once redirected back to `/api/internal/v1/complete/google-oauth2`, this will complete the OAuth2 flow. At this point, the backend has access to several pieces of information about the Google user, including their `access_token` and `refresh_token`. We persist these (encrypted) for future use to fetch the user's out-of-office calendar events 5. The response from the API call in 4 above ☝️ is HTTP 302 (redirect) to `/a/grafana-oncall-app/users/me` (ie. open the user profile settings modal). At this point the user will see that their account has been connected and they can further configure the settings ![image](https://github.com/grafana/oncall/assets/9406895/c7673055-8485-4f9a-98df-b4f7347229ce) ## Which issue(s) this PR closes Closes https://github.com/grafana/oncall-private/issues/2584 ## Checklist - [x] Unit, integration, and e2e (if applicable) tests updated - [x] Documentation added (or `pr:no public docs` PR label added if not required) - will be done in https://github.com/grafana/oncall-private/issues/2591 - [x] Added the relevant release notes label (see labels prefixed w/ `release:`). These labels dictate how your PR will show up in the autogenerated release notes. - will be done in https://github.com/grafana/oncall-private/issues/2591 --------- Co-authored-by: Dominik <dominik.broj@grafana.com> Co-authored-by: Maxim Mordasov <maxim.mordasov@grafana.com>
2024-04-02 14:59:03 -04:00
google-api-python-client==2.122.0
google-auth-httplib2==0.2.0
google-auth-oauthlib==1.2.0
Reference in a new issue Copy permalink