From f66f5600b705566182f2efed5a18c55dba6f6d6a Mon Sep 17 00:00:00 2001
From: Brian Phillips <28457+brianphillips@users.noreply.github.com>
Date: Fri, 19 Apr 2024 11:34:52 -0500
Subject: [PATCH] Use pagerduty-specific moduleId

The previous value (custom-extensions) conflicts with the example value from the [backstage documentation for writing custom actions](https://backstage.io/docs/features/software-templates/writing-custom-actions#register-action-with-new-backend-system). This value should be specific to this module.
---
 src/module.ts | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/module.ts b/src/module.ts
index 5e392f1..2c3e804 100644
--- a/src/module.ts
+++ b/src/module.ts
@@ -6,7 +6,7 @@ import { createPagerDutyServiceAction } from "./actions/custom";
 /** @public */
 export const pagerDutyScaffolderActions = createBackendModule({
     pluginId: 'scaffolder',
-    moduleId: 'custom-extensions',
+    moduleId: 'pagerduty-actions',
     register(env) {
         env.registerInit({
             deps: {
@@ -23,4 +23,4 @@ export const pagerDutyScaffolderActions = createBackendModule({
             },
         });
     },
-});
\ No newline at end of file
+});