JSPM

serverless-aws-resolver

0.0.2
  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 200
  • Score
    100M100P100Q81682F
  • License MIT

Resolve AWS variables in Serverless when you don't want to actually make a call to AWS

Package Exports

  • serverless-aws-resolver
  • serverless-aws-resolver/index.js

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (serverless-aws-resolver) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

serverless-aws-resolver

Resolve AWS variables in Serverless when you don't want to actually make a call to AWS

This plugin allows CloudFormation and SSM variables to be used even totally offline. Normally these variables are fetched from AWS during the Serverless packaging stage, but when this plugin is enabled it will intercept the requests to AWS and return the values from your custom config.

This is useful when you want to build a stack in an environment that doesn't have access to AWS, such as test environments or environments which are completely offline.

Example config:

plugins:
  - serverless-aws-resolver # You'll probably want this at the top of plugins list

custom:
  serverless-aws-resolver:
    stages:
      - dev # The stages where you want to enable this plugin
    ssm: # SSM
      /some-path/SOME_SSM_KEY: 'Your String Value' # The key and value you want to provide  
    cf: # Cloudformation
      service-resources-dev: # The Cloudformation stack name
        AlarmsSNSTopic: Foo # Key and value you want to provide
        SomethingElse: Bar
    aws:
      accountId: 123456789012 # Currently only accountId is the only supported AWS variable

Todo

  • Add tests
  • Rewrite in TypeScript
  • Better checks, it's currently pretty sloppy
  • Add support for other AWS variables like S3