Antoine Grenard
Antoine Grenard

Reputation: 1892

NestJs Using Environment Configuration on @Cron decorator

I am building a nestJs application, with scheduling and configuration. I want to be able to configure my Cron with my environment variable but it does not seems to work.

app.module.ts :

@Module({
  imports: [
    ConfigModule.forRoot(),
    ScheduleModule.forRoot(),
    SchedulingModule,
    ...
  ],
})
export class AppModule {}

scheduling.service.ts (from my SchedulingModule) :

@Cron(process.env.CRON_VALUE)
scheduledJob() {
  this.logger.log('Scheduled : Job');
  ...
}

.env :

...
CRON_VALUE=0 4 * * *
...

Apparently at the moment the value is checked it's empty. I got the following error :

(node:55016) UnhandledPromiseRejectionWarning: TypeError: Cannot read property '_isAMomentObject' of undefined
    at new CronTime (/Users/antoinegrenard/Documents/Projet/b4finance/service-scheduling/node_modules/cron/lib/cron.js:42:50)
    at new CronJob (/Users/antoinegrenard/Documents/Projet/b4finance/service-scheduling/node_modules/cron/lib/cron.js:527:19)
    at /Users/antoinegrenard/Documents/Projet/b4finance/service-scheduling/node_modules/@nestjs/schedule/dist/scheduler.orchestrator.js:56:29 
    ...

Upvotes: 3

Views: 7849

Answers (3)

Jon Martins
Jon Martins

Reputation: 65

A way I made it work was like this

import * as dotenv from 'dotenv';

const getCronInterval = () => {
  dotenv.config();

  return process.env.FETCH_AND_SEND_DATA_CRON_INTERVAL;
};

@Injectable()
export class AppService {
  constructor(
    private readonly service: MyService,
  ) {}

  @Cron(getCronInterval()) // Adjust the cron schedule as needed
  async doSomething() {
    ....

Upvotes: 0

Antoine Grenard
Antoine Grenard

Reputation: 1892

Apparently it is not possible to get env values in decorators.

I had to do it this way :

constructor(private schedulerRegistry: SchedulerRegistry) {}

onModuleInit() {
  const job = new CronJob(process.env. CRON_VALUE, () => {
    // What you want to do here
  });

  this.schedulerRegistry.addCronJob(name, job);
  job.start();
}

Upvotes: 12

Ayoub Touba
Ayoub Touba

Reputation: 2987

To fix this problem you should load the config on your service again:

require('dotenv').config();

Upvotes: 1

Related Questions