Macro Custom Pragma Runner

A macro for @architect/architect that lets you define and run custom pragmas intuitively.

Installation

From source

npm install zibasec/macro-custom-pragma-runner

Note: npm version coming soon...

Usage

Define your custom pragma in .arc, ensure the name is prefixed by an underscore.

Sample .arc file this has a @_hello

@app
myApp

@http
post /hellow

@macros
macro-custom-pragma-runner

@_hello
name Julie

Ensure the directory src/pragmas/ exists.

Ensure that you make either src/pragmas/hello.js or src/pragmas/hello/index.js

Then within that file define a function that returns a Promise. This function will receive the object { arc, cloudformation, stage, args } as an argument. These will have the same shape as explained in the Architect for custom macros docs. args is the raw shape of the parsed arguments for your pragma.

Given arguments like this:

@_hello
name Julie
details:
  favoriteColor: green

the value of args would look like

[ [ 'name', 'Julie' ],
  { 'details:': { 'favoriteColor:': 'green' } } ]

It can optionally return an object with a cloudformation property, this value will be merged with the architect generated property via Object.assign().

Example:

module.exports = async function ({ arc, cloudformation, stage, args }) {
  console.log(`Hello ${args[0][1]}`)
  // this return statement isn't needed since we're not modifying the cft but it's here for demonstration
  return { cloudformation }
}

Next time your run npx arc deploy you should see Hello Julie in stdout.

IMPORTANT the custom pragams are executed in the order in which they are defined. This can cause issues if multiple custom pragmas modify the same cloudformation properties.

Creating and Installing Custom Pragmas

You can also publish pragams to any npm-compatible package manager.

Given an .arc file that looks like this:

@app
myHookApp

@http
post /hook

@macros
macro-custom-pragma-runner

@_zibasec/arc-http-raw-body
post /hook

@aws
region us-east-1

This macro will look in the following directories, in order, for the custom pragma _zibasec/arc-http-raw-body

1. ./src/pragmas/_zibasec/arc-http-raw-body
2. ./src/pragmas/zibasec/arc-http-raw-body
3. ./node_modules/_zibasec/arc-http-raw-body (implies installation via npm install _zibasec/arc-http-raw-body)
4. ./node_modules/@_zibasec/arc-http-raw-body (implies installation via npm install @_zibasec/arc-http-raw-body)
5. ./node_modules/zibasec/arc-http-raw-body (implies installation via npm install zibasec/arc-http-raw-body)
6. ./node_modules/@zibasec/arc-http-raw-body (implies installation via npm install @zibasec/arc-http-raw-body)

Again, the same rule applies. In packaged-form, your pragma must still contain a root-level index.js with a default export.

License

MIT