@byaga/cdk-patterns 0.11.5 → 0.11.6

package/archive/methods/attach-function-to-api.ts

@@ -1,69 +0,0 @@
-import {DeployStack} from "../DeployStack";
-import {
-    JsonSchema,
-    LambdaIntegration,
-    MethodOptions,
-    IResource, Method
-} from "aws-cdk-lib/aws-apigateway";
-import {RestApi} from "../RestApi";
-import {applySchemaToMethodOptions} from "./apply-schema-to-method-options";
-import {FunctionIntegration} from "../create-function";
-
-/**
- * Type alias for the properties when attaching a function to an API or a resource.
- */
-type AttachFunctionToApiProps = AttachFunctionToRestApiProps | AttachFunctionToResourceProps
-
-/**
- * Interface for the properties when attaching a function to an API.
- */
-export interface AttachFunctionToRestApiProps {
-    api: RestApi
-    httpMethod: string
-    path: string
-    requestSchema?: JsonSchema,
-    methodOptions?: MethodOptions
-}
-
-/**
- * Interface for the properties when attaching a function to a resource.
- */
-export interface AttachFunctionToResourceProps {
-    resource: IResource
-    httpMethod: string
-    requestSchema?: JsonSchema,
-    methodOptions?: MethodOptions
-}
-
-export interface ApiAttachedFunction extends FunctionIntegration {
-    resourceArn: string
-    method: Method
-}
-
-/**
- * Attaches a function to an API or a resource.
- * @param {DeployStack} stack - The deployment stack.
- * @param lambda - The Function that is being attached
- * @param {AttachFunctionToApiProps} props - The properties for attaching the function.
- * @returns {ApiAttachPoint} The API attach point.
- */
-export function attachFunctionToApi(stack: DeployStack, lambda: FunctionIntegration, props: AttachFunctionToApiProps) : ApiAttachedFunction {
-    const resource: IResource = (props as AttachFunctionToResourceProps).resource || (props as AttachFunctionToRestApiProps).api.path((props as AttachFunctionToRestApiProps).path)
-    const integration = new LambdaIntegration(lambda.function, {
-        requestTemplates: {
-            'application/json': '{ "statusCode": "200" }'
-        }
-    })
-
-    let options: MethodOptions = props?.methodOptions || {}
-    const schema = props?.requestSchema
-    if (schema) options = applySchemaToMethodOptions(stack, lambda.id, schema, options, resource)
-
-    const method = resource.addMethod(props.httpMethod, integration, options)
-
-    return {
-        ...lambda,
-        method,
-        resourceArn: `arn:aws:execute-api:${stack.region}:${stack.account}:${resource.api.restApiId}/${stack.stage}/${props.httpMethod}${resource.path}`
-    };
-}

package/lib/create-stack.d.ts

@@ -1,40 +0,0 @@
-import { IConstruct } from "constructs";
-import { Stack } from "aws-cdk-lib";
-import { StackProps } from "aws-cdk-lib/core";
-import { StackConfiguration } from "./load-configuration";
-/**
- * Interface for the arguments when creating a stack.
- */
-export interface StackArguments extends StackProps {
-    stackName: string;
-    stage?: string;
-    project: string;
-    owner: string;
-    region: string;
-}
-/**
- * Interface for the stack.
- */
-export interface DeployStack<T extends StackConfiguration> {
-    stack: Stack;
-    name: string;
-    stage: string;
-    project: string;
-    config: Partial<T>;
-}
-/**
- * Creates a new stack.
- * @param {IConstruct} scope - The scope in which to define this construct.
- * @param {StackArguments} props - The arguments for creating the stack.
- * @returns {DeployStack} The created stack.
- */
-export declare function createStack<T extends StackConfiguration>(scope: IConstruct, props: StackArguments): DeployStack<T>;
-/**
- * Helpful method to get the 'current' stack that is being defined.  Hopefully this will reduce the need to pass the stack around everywhere.
- */
-export declare function getCurrentStack<T extends StackConfiguration>(): DeployStack<T>;
-/**
- * This sets the 'current' stack.  This should be automatic everywhere, but in case something goes wrong here is a way to force the issue
- * @param stack
- */
-export declare function setCurrentStack<T extends StackConfiguration>(stack: DeployStack<T>): DeployStack<T>;

package/lib/create-stack.js

@@ -1,48 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.setCurrentStack = exports.getCurrentStack = exports.createStack = void 0;
-const aws_cdk_lib_1 = require("aws-cdk-lib");
-const generate_identifier_1 = require("./generate-identifier");
-const load_configuration_1 = require("./load-configuration");
-/**
- * Creates a new stack.
- * @param {IConstruct} scope - The scope in which to define this construct.
- * @param {StackArguments} props - The arguments for creating the stack.
- * @returns {DeployStack} The created stack.
- */
-function createStack(scope, props) {
-    const { stage = 'develop' } = props;
-    const stack = new aws_cdk_lib_1.Stack(scope, (0, generate_identifier_1.genId)(props.stackName, stage), {
-        ...props,
-        stackName: (0, generate_identifier_1.genName)(props.stackName, stage)
-    });
-    stack.tags.setTag('stage', stage);
-    stack.tags.setTag('stack', (0, generate_identifier_1.genName)(props.stackName, stage));
-    stack.tags.setTag('project', props.project);
-    stack.tags.setTag('owner', props.owner);
-    return setCurrentStack({
-        stack,
-        name: props.stackName,
-        stage,
-        project: props.project,
-        config: (0, load_configuration_1.loadConfiguration)(stage)
-    });
-}
-exports.createStack = createStack;
-let currentStack;
-/**
- * Helpful method to get the 'current' stack that is being defined.  Hopefully this will reduce the need to pass the stack around everywhere.
- */
-function getCurrentStack() {
-    return currentStack;
-}
-exports.getCurrentStack = getCurrentStack;
-/**
- * This sets the 'current' stack.  This should be automatic everywhere, but in case something goes wrong here is a way to force the issue
- * @param stack
- */
-function setCurrentStack(stack) {
-    currentStack = stack;
-    return stack;
-}
-exports.setCurrentStack = setCurrentStack;