1.0.1 • Published 9 months ago
@effect-aws/client-scheduler v1.0.1
@effect-aws/client-scheduler
Installation
npm install --save @effect-aws/client-scheduler
Usage
With default SchedulerClient instance:
import { SchedulerService, DefaultSchedulerServiceLayer } from "@effect-aws/client-scheduler";
const program = SchedulerService.tagResource(args);
const result = pipe(
program,
Effect.provide(DefaultSchedulerServiceLayer),
Effect.runPromise,
);
With custom SchedulerClient instance:
import {
SchedulerService,
BaseSchedulerServiceLayer,
SchedulerClientInstance,
} from "@effect-aws/client-scheduler";
const program = SchedulerService.tagResource(args);
const SchedulerClientInstanceLayer = Layer.succeed(
SchedulerClientInstance,
new SchedulerClient({ region: "eu-central-1" }),
);
const result = await pipe(
program,
Effect.provide(BaseSchedulerServiceLayer),
Effect.provide(SchedulerClientInstanceLayer),
Effect.runPromise,
);
With custom SchedulerClient configuration:
import {
SchedulerService,
BaseSchedulerServiceLayer,
DefaultSchedulerClientConfigLayer,
SchedulerClientInstance,
SchedulerClientInstanceConfig,
} from "@effect-aws/client-scheduler";
const program = SchedulerService.tagResource(args);
const SchedulerClientInstanceLayer = Layer.provide(
Layer.effect(
SchedulerClientInstance,
SchedulerClientInstanceConfig.pipe(
Effect.map(
(config) => new SchedulerClient({ ...config, region: "eu-central-1" }),
),
),
),
DefaultSchedulerClientConfigLayer,
);
const result = await pipe(
program,
Effect.provide(BaseSchedulerServiceLayer),
Effect.provide(SchedulerClientInstanceLayer),
Effect.runPromiseExit,
);
or map over DefaultSchedulerClientConfigLayer
layer context and update the configuration...