Opsgenie team responders support #43535
Conversation
Signed-off-by: edward <edward@edwards-MacBook-Pro.local>
EdwardDowling
force-pushed
the
edwarddowling/43281
branch
from
403435b to
4eaf615
Compare
|
🤖 Vercel preview here: https://docs-kculvdcp4-goteleport.vercel.app/docs/ver/preview |
|
🤖 Vercel preview here: https://docs-1w3eby5m0-goteleport.vercel.app/docs/ver/preview |
github-actions
bot
requested review from
hugoShaka,
marcoandredinis,
mmcallister,
nklaassen,
ptgott,
r0mant,
tigrato,
xinding33 and
zmb3
|
The PR changelog entry failed validation: Changelog entry not found in the PR body. Please add a "no-changelog" label to the PR, or changelog lines starting with |
|
The PR changelog entry failed validation: Changelog entry not found in the PR body. Please add a "no-changelog" label to the PR, or changelog lines starting with |
|
🤖 Vercel preview here: https://docs-irjv4fnum-goteleport.vercel.app/docs/ver/preview |
|
Can we add a case in the test suite for this? |
Signed-off-by: Edward Dowling <edward.dowling@goteleport.com>
EdwardDowling
force-pushed
the
edwarddowling/43281
branch
from
585f0f9 to
c96e67b
Compare
|
The PR changelog entry failed validation: Changelog entry not found in the PR body. Please add a "no-changelog" label to the PR, or changelog lines starting with |
|
🤖 Vercel preview here: https://docs-ox3b6zmos-goteleport.vercel.app/docs/ver/preview |
|
🤖 Vercel preview here: https://docs-dzmvyp2yg-goteleport.vercel.app/docs/ver/preview |
|
🤖 Vercel preview here: https://docs-1ngl2sh8m-goteleport.vercel.app/docs/ver/preview |
|
🤖 Vercel preview here: https://docs-9tp20eppz-goteleport.vercel.app/docs/ver/preview |
|
🤖 Vercel preview here: https://docs-3pzm6d1ea-goteleport.vercel.app/docs/ver/preview |
|
🤖 Vercel preview here: https://docs-16061jmkt-goteleport.vercel.app/docs/ver/preview |
|
@EdwardDowling See the table below for backport results.
|
Signed-off-by: Edward Dowling <edward.dowling@goteleport.com> Co-authored-by: Carlos Castro <carlos.castro@jumo.world>
* Opsgenie team responders support (#43535) Signed-off-by: Edward Dowling <edward.dowling@goteleport.com> Co-authored-by: Carlos Castro <carlos.castro@jumo.world> * Split schedules/teams into seperate alerts * Update integrations/access/opsgenie/app.go Co-authored-by: Nic Klaassen <nic@goteleport.com> * aUpdate integrations/access/opsgenie/app.go Co-authored-by: Nic Klaassen <nic@goteleport.com> --------- Signed-off-by: Edward Dowling <edward.dowling@goteleport.com> Co-authored-by: Carlos Castro <carlos.castro@jumo.world> Co-authored-by: Nic Klaassen <nic@goteleport.com>
Buddy PR for 43281
Currently, when creating an Opsgenie alert with the Opsgenie integration, responders can only be of type
schedule.However that are situations where type
teamsare required to work with Opsgenie integrations, as well, teams takes multiple schedules into consideration, such as escalations schedules.Instead of changing the
teleport.dev/notify-servicesannotation to support teams by default, I purpose adding a new annotationteleport.dev/teamsthat will contains the respective teams and the result will be a merge of both annotations to the responders payload.Teleport role:
will be converted into Opsgenie payload
{ "message": "Access request from ...", "alias": "....", "description":"....", "responders":[ {"name":"MySchedule", "type":"schedule"}, {"name":"MyTeam", "type":"team"} ], "priority":"P2" }Changelog: Add support for Teams to Opsgenie plugin alert creation