Upgrade Guide

Guides for upgrading to the latest version of Architect


Architect version 5 is here!

Things we added:


Architect version 4 (Yeti) is here!

Things we added:

  • /public for static assets
  • @http routes
  • complete docs overhaul
  • new simpler install package npm i @architect/architect
  • one repo architect/architect
  • @architect/functions new APIs: arc.http, arc.http.session and arc.http.helpers

Things we removed:

  • Statically bound Content-Type routes: @html, @css, @js, @json, @text, @xml
  • @architect/functions interfaces: arc.css, arc.js, etc.

Upgrading to HTTP functions

HTTP functions are now completely dynamic and allow for either async/await or Node style errback signatures with zero deps.

Extremely new school style:

exports.handler = async function http(request) {
  return {
    cors: true,
    type: 'application/javascript',
    body: JSON.stringify({hello:'world'})

Extremely old school style:

exports.handler = function http(request, context, callback) {
  callback(null, {
    cors: true,
    type: 'application/javascript',
    body: JSON.stringify({hello:'world'})

Of course the aws-sdk, and @architect/functions and @architect/data are still available should you wish to opt into richer functionality. Session support is much more granular:

let arc = require('@architect/functions')

exports.handler = async function http(request) {

  // read the session from DynamoDB
  let session = await arc.http.session.read(request)

  // mutate the session state
  session.like = (session.like || 0) + 1

  // write the session to DynamoDB and get a Set-Cookie string
  let cookie = await arc.http.session.write(session)

  // ensure the cookie gets updated on the client
  return {
    cors: true,
    type: 'application/javascript',
    body: JSON.stringify({hello:'world'})

The old school express-style middleware is still available with @architect/functions:

let arc = require('@architect/functions')
let url = arc.http.helpers.url

function log(req, res, next) {
  console.log('logger middleware:', JSON.stringify(req, null, 2))

function route(req, res) {
    html: `hello world from ${url(req.path)}`

exports.handler = arc.http(log, route)

Deprecated Docs


@architect/workflows added SQS support in 3.3.0 and existing apps will need to add permissions to the default arc-role IAM Role used for Lambda execution if they want to add @queues.

Using the AWS Console

  1. Open up IAM in the AWS Console
  2. Select Rolesarc-role
  3. Click Attach Policies
  4. Select AWSLambdaSQSQueueExecutionRole
  5. Click Attach Policy

Now existing functions can publish to SQS queues.

With the AWS CLI

If the command line is more your style you can upgrade with the following:

aws iam attach-role-policy --policy-arn arn:aws:iam::aws:policy/service-role/AWSLambdaSQSQueueExecutionRole --role-name arc-role

With NodeJS

If you prefer to script this upgrade you can use the NodeJS aws-sdk:

let aws = require('aws-sdk')
let PolicyArn = 'arn:aws:iam::aws:policy/service-role/AWSLambdaSQSQueueExecutionRole'

let iam = new aws.IAM
  RoleName: 'arc-role'
}, console.log)