Fix panic in pagerduty plugin init phase (#46924)

This PR fixes a problem caused by pagerduty not having the Teleport
client initialized when starting from the standalone plugin.

This PR fixes the issue by moving the access monitoring rules init
function to a place where the teleport client is already initialized.

Signed-off-by: Tiago Silva <[email protected]>

integrations/access/pagerduty/app.go

@@ -78,18 +78,7 @@ func NewApp(conf Config) (*App, error) {
 		teleport:   conf.Client,
 		statusSink: conf.StatusSink,
 	}
-	app.accessMonitoringRules = accessmonitoring.NewRuleHandler(accessmonitoring.RuleHandlerConfig{
-		Client:     conf.Client,
-		PluginType: types.PluginTypePagerDuty,
-		PluginName: pluginName,
-		FetchRecipientCallback: func(_ context.Context, name string) (*common.Recipient, error) {
-			return &common.Recipient{
-				Name: name,
-				ID:   name,
-				Kind: common.RecipientKindSchedule,
-			}, nil
-		},
-	})
+
 	app.mainJob = lib.NewServiceJob(app.run)
 
 	return app, nil
@@ -184,6 +173,19 @@ func (a *App) init(ctx context.Context) error {
 		}
 	}
 
+	a.accessMonitoringRules = accessmonitoring.NewRuleHandler(accessmonitoring.RuleHandlerConfig{
+		Client:     a.teleport,
+		PluginType: types.PluginTypePagerDuty,
+		PluginName: pluginName,
+		FetchRecipientCallback: func(_ context.Context, name string) (*common.Recipient, error) {
+			return &common.Recipient{
+				Name: name,
+				ID:   name,
+				Kind: common.RecipientKindSchedule,
+			}, nil
+		},
+	})
+
 	if pong, err = a.checkTeleportVersion(ctx); err != nil {
 		return trace.Wrap(err)
 	}