feat: support Zenduty integration key alongside existing API token#223
Merged
kunalnagar merged 1 commit intomainfrom Apr 14, 2026
Merged
feat: support Zenduty integration key alongside existing API token#223kunalnagar merged 1 commit intomainfrom
kunalnagar merged 1 commit intomainfrom
Conversation
Add sendAlertsToZendutyViaIntegration using the events API endpoint (https://events.zenduty.com/api/events/<key>/), which only requires a single zenduty_integration_key input rather than api_key + service_id + escalation_policy_id. Integration key is preferred when provided; falls back to the existing incidents API path for backwards compatibility. Also fix action.yml numeric defaults (587, 20) to strings as required. Closes #135.
|
🎉 This issue has been resolved in version 1.16.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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
1 participant
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.
Summary
zenduty_integration_keyinput that uses the Zenduty Events API (https://events.zenduty.com/api/events/<key>/) — no auth header needed, just the key in the URLzenduty_integration_keyis provided it takes precedence; falls back to the existingzenduty_api_key+zenduty_service_id+zenduty_escalation_policy_idpath for backwards compatibilityaction.ymldescriptionsaction.ymlnumeric defaults (587,20) to strings as required by the schemaNo breaking changes — existing users are unaffected.
Closes #135
Test plan
npm testpasses (58 tests across 9 files)npm run buildpasses with no type errorsnpx eslint src/**/*.ts tests/**/*.tspasses with no errors