Release/2.0 - #67
Merged
Merged
Conversation
…entication (401 response) instead of forbidden (403).
- Implements Uptime Kuma normalizer for state mapping, severity, and tag handling. - Adds comprehensive test coverage for normalizer, route behavior, lifecycle, and payload validation. - Includes full integration guide and troubleshooting in the documentation. - Registers UI updates and API paths for the new integration.
* Document the Kubernetes/Helm installation The chart in helm/incidentrelay had no documentation page: the only mention was a short section in the README, and getting-started listed Docker, RPM and systemd as the available methods. Add getting-started/kubernetes.md covering what the chart deploys, how values map onto incidentrelay.conf, the SQLite and PostgreSQL setups, migrations and web scaling, probes, ingress, workers and uninstall caveats. Mirror it into docs/ru and link it from the installation dispatchers, the mkdocs nav and the README. * Document the Slack Socket Mode worker in the Kubernetes guide
* Add Slack Socket Mode worker deployment to the Helm chart
The entrypoint has supported INCIDENTRELAY_SERVICE=slack since the
worker was introduced and docker-compose runs it, but the chart never
shipped a Deployment for it. As a result Slack interactive buttons
(Acknowledge and friends) were dead on Kubernetes: the web pod posted
messages, and nothing consumed the Socket Mode WebSocket.
Add deployment-slack.yaml mirroring the telegram worker, along with the
matching `slack` values block and a line in NOTES.txt.
Verified on a kind cluster: the pod reconciles channel config from the
database without a restart ("Slack Socket Mode connection started",
channel_count 1), and an alert delivered through a webhook route can be
acknowledged from Slack.
* Bump chart version to 1.2.0 for the Slack worker deployment
…lement notification handling refinements for heartbeat recovery scenarios. #34
… helpers across API, UI, and tests. #37
- Introduced `apply_to_existing` field for silences to retroactively suppress unresolved alerts. - Updated database schema, migration scripts, and models for retroactive silence behavior. - Expanded API endpoints to support retroactive silence application and reconciliation. - Enhanced UI to expose retroactive silence functionality in forms and details. - Added comprehensive test coverage for retroactive silences across lifecycle workflows. - Updated localization files for new retroactive silence messages. - Adjusted incident management documentation to detail retroactive silence handling. Part 2 of #37
…tests, enhance integrations and documentation - Introduced robust handling of `suppress_notifications` maintenance behavior across notification, reminder, and escalation workflows. - Added `pause_notification_lifecycle` and `resume_notification_lifecycle` utilities to manage maintenance states. - Enhanced repository models, schedulers, and APIs to respect maintenance lifecycle suppression. - Developed comprehensive test cases for reminder suppression, notification lifecycle pausing, and escalation timing adjustments. - Updated documentation for maintenance behaviors, escalation policies, and integrations. - Added Datadog and Uptime Kuma entries in integrations and README. #40
- Implemented locale and theme fields in the user model and database schema with default values. - Added migration scripts for updating the database to include new fields. - Updated profile endpoints and serializers to manage locale and theme preferences. - Enhanced UI to allow users to select and save their preferred language and theme. - Updated front-end logic to apply selected preferences dynamically. - Included localization updates and dark theme styles for the user interface. - Added test coverage for preference validation, API behavior, and UI rendering. #43
…maintenance windows and silences - Updated database schema, migrations, and models to include new fields for lifecycle control. - Enhanced APIs, serializers, and UI to support `reactivate_on_end` and `apply_to_existing`. - Implemented comprehensive lifecycle reconciliation for maintenance windows and silences. - Improved test coverage for lifecycle reconciliation, retention, and reactivation scenarios. - Updated documentation to detail the new lifecycle options, behaviors, and API changes. #41
- Introduced unit tests for SSO mapping edit form behavior and OIDC mapping rule updates. - Refactored JavaScript logic to simplify role assignment using `.val()` and `??` for default values. - Improved test coverage for mapping role, team, and priority updates. - Ensured consistency and validity of mapping updates in API and UI workflows. #42
`openExistingSsoMappingModal()` called `.valssoRoleLabel(...)` on the two role selects — a mashed-together `.val(` and `ssoRoleLabel(`. The call threw `TypeError: $(...).valssoRoleLabel is not a function` before `openAppModal()` was reached, so clicking Edit on a mapping did nothing and rules could only be re-created. Set the select values directly. `ssoRoleLabel()` returns a translated display label, not an option value, so it was the wrong helper here regardless of the syntax error. Also add tests for `PUT /api/admin/sso/mappings/<id>`, which had no coverage: full update with team attach, team detach clearing team_role, and rejecting a team that belongs to another group. Fixes #42
…h handling, splitting, and variable manipulation - Expanded action types to include `extract_regex`, `json_path`, `split`, `set_variable`, and transformations like `lowercase`, `uppercase`, and `trim`. - Enhanced UI to dynamically render configuration inputs based on action type. - Added field, pattern, delimiter, and value handling for new actions in orchestration workflows. - Incorporated logic to map inputs into properly structured action objects during orchestration. - Introduced screenshots for updated orchestration configuration UI.
…grity - Added unit tests for dependency graph service separation and status helpers. - Introduced tests for escalation policy rule handling, delay normalization, and user resolution. - Implemented release integrity tests to guard against Python symbol and JavaScript function shadowing. - Updated OpenAPI alert comment schema tests to validate constraints.
add shared as_utc_naive, as_utc_naive_seconds, and utc_now_seconds helpers replace duplicated UTC normalization logic across heartbeats, on-call, calendar, silences, business services, and orchestrations normalize heartbeat timestamps to whole-second precision to avoid microsecond comparison inconsistencies support naive datetimes, timezone-aware datetimes, and ISO timestamps through the same normalization path preserve the existing naive UTC storage convention add regression tests for UTC conversion, ISO timestamps, precision handling, and duplicated datetime helpers
…s and standardize UTC handling - Added `rotation_schedule.py` module to centralize scheduling functions, including slot indexing, boundary calculation, layer value retrieval, and timezone handling. - Replaced duplicated logic for datetime and timezone processing with shared helpers. - Updated serializers to use `serialize_utc_datetime` for consistent UTC formatting. - Enhanced unit tests for datetime conversions, including edge cases for timezones, DST, and ISO string support. - Simplified on-call, calendar, and heartbeats services with reusable rotation scheduling utilities.
- Added `api_token_scopes.py` to consolidate scope definitions, request-scoping rules, and utility functions. - Introduced granular read/write scopes for finer access control per resource domain. - Migrated legacy aggregate scopes (`resources:read/write`) for backward compatibility. - Updated APIs, middleware, and token workflows to utilize centralized scope logic. - Enhanced profile UI and API to surface selectable token scopes based on privileges. - Added test coverage for scope mapping, token delegation, and access validation. #62
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
…caping or encoding' Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.