npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

pollen.tech-appsync-codegen

v0.0.3

Published

Pollen Appsync Codegen for development use

Downloads

2

Readme

Pollen Core AppSync

This project contains AppSync deployment and resolvers for AppSync APIs

Requirements

  1. Terraform

Add / Update AWS AppSync Configuration

  1. Add or update schema on schema.graphql located on ./appsync/schema.graphql

  2. Add or update AppSync Resolver located on ./terraform/modules/appsync/resolvers. Note: 1 Folder per resolver

  3. Create resolver with minimum file requirement as follows:

    └── resolvers (main resolver folder)/
        └── your-resolver/
            ├── resolvers/
            │   ├── request.vtl
            │   └── response.vtl
            ├── main.tf
            └── variable.tf

    main.tf contains AppSync Resolver and Datasource configuration

    resource "aws_appsync_datasource" "<datasource name>" {
        name             = <datasource name>
        api_id           = var.api_id
        type             = <datasource_type>
        service_role_arn = var.appsync.iam_role_arn
        lambda_config {
            function_arn = <AWS Lambda ARN>
        }
    }
    
    # Create resolver using the velocity templates in /resolvers/lambda.
    resource "aws_appsync_resolver" "<resolver name>" {
        api_id      = var.api_id
        type        = <resolver for schema type>
        field       = <resolved field>
        data_source = aws_appsync_datasource.get_catalog.name
    
        request_template  = file("${path.module}/resolvers/request.vtl")
        response_template = file("${path.module}/resolvers/response.vtl")
    }
    

    variable.tf contains variable that used by main.tf

    variable "api_id" {
        default = ""
        description = "appsync api id"
    }
    
    variable "appsync" {
       description = "appsync properties"
    }

    New files or new configuration inside those files can be added as needed

  4. Add your AppSync resolver on main.tf file inside modules/appsync folder. Open ./terraform/modules/appsync/main.tf

    # ...
    # ...
    # ...
    module "<your new resolver>" {
        source  = "./resolvers/<your new resolver on ./terraform/modules/appsync/resolvers>"
        api_id  = aws_appsync_graphql_api.staging.id
        appsync = var.appsync
    }