update: Pulumi configurations and ECS task definition

Author: winverse

infrastructure/Pulumi.production.yaml

@@ -1,4 +1,4 @@
 config:
   aws:region: ap-northeast-2
   velog:DOCKER_ENV: production
-  velog:target: cron
+  velog:target: server

infrastructure/Pulumi.stage.yaml

@@ -1,4 +1,4 @@
 config:
   aws:region: ap-northeast-2
   velog:DOCKER_ENV: stage
-  velog:target: server,web
+  velog:target: server

infrastructure/src/common/ecs.ts

@@ -40,8 +40,8 @@ export const createECSfargateService = ({
         subnets: subnetIds,
       },
       taskDefinitionArgs: {
-        cpu: option.taskCpu,
-        memory: option.taskMemory,
+        // cpu: option.taskCpu,
+        // memory: option.taskMemory,
         executionRole: {
           roleArn: ecsTaskExecutionRole.arn,
         },

packages/velog-server/src/common/plugins/global/mercuriusPlugin.ts

@@ -54,7 +54,7 @@ const mercuriusPlugin: FastifyPluginAsync = async (fastify) => {
       const e = execution.errors?.[0]?.originalError
 
       if (!isHttpError(e)) {
-        console.log('send!')
+        console.log('mecurius errorFormatter')
         ;(ctx as any).request?.log?.error(execution, 'errorFormatter')
         const discord = container.resolve(DiscordService)
         discord