How to reference serverless variables in bash script

[grayaii]

This is a question, not an issue. I see that this plugin supports running bash scripts.

My serverless.yml creates some AWS resources. I want my bash script to know the ARN's of those various resources.

Is this possible? Is there an example of this?

Thanks!

[weixu365]

I'm not sure if there's a simple way to get the ARNs, what I tried before is:

• Add resources to Output in serverless.yml
• Using AWS sdk/cli to get resources in your script

[andreimcristof]

hi, I was trying to find out how to do this too (I need to get the names and urls that are created for funcitons, api gateway etc, in an "after" script when everything is done), I see the README example referencess serverless variable:

const resources = serverless.service.provider.compiledCloudFormationTemplate.Resources;

but in the .js script it throws with serverless undefined. could you please shed light on how to expose the serverless variable to fetch all configs created? Thanks,

[weixu365]

@andreimcristof

You can try the following config and script:

serverless.yml

service: demo

provider:
  name: aws
  runtime: nodejs8.10
  region: ap-southeast-2

plugins:
  - serverless-scriptable-plugin

custom:
  scriptHooks:
    after:aws:deploy:finalize:cleanup: ./geturl.js

functions:
  test:
    handler: handler.handle

geturl.js

const AWS = require("aws-sdk");

// You can find out all the resources, filter by type
const resources = serverless.service.provider.compiledCloudFormationTemplate.Resources;
Object.keys(resources)
  // .filter(name => resources[name].Type === 'AWS::Logs::LogGroup')
  .forEach(r => console.log(r));

// Using aws sdk to find out the resource info, I'm using lambda function as an example.
// You can change to API Gateway to get the physical id
let cloudformation = new AWS.CloudFormation({ region: 'ap-southeast-2' });
cloudformation.describeStackResource({
  LogicalResourceId: 'TestLambdaFunction',
  StackName: `${serverless.service.service}-${serverless.service.provider.stage}`,
}).promise()
  .then(response => console.log(response['StackResourceDetail']));

Output on my machine:

Running javascript file: ./geturl.js
ServerlessDeploymentBucket
TestLogGroup
IamRoleLambdaExecution
TestLambdaFunction
TestLambdaVersionZ8Wrs8X2xzZU1YAYTIxrQOLG7KCbTrioAWqTUNLWqVc
{ StackName: 'demo-dev',
  StackId: 'arn:aws:cloudformation:ap-southeast-2:xxxx:stack/demo-dev/010dfda0-d47f-11e9-bc6d-0230e8e86e24',
  LogicalResourceId: 'TestLambdaFunction',
  PhysicalResourceId: 'demo-dev-test',
  ResourceType: 'AWS::Lambda::Function',
  LastUpdatedTimestamp: 2019-09-11T10:53:56.807Z,
  ResourceStatus: 'UPDATE_COMPLETE',
  Metadata: '{}',
  DriftInformation: { StackResourceDriftStatus: 'NOT_CHECKED' } }

Available Serverless lifecycle events: https://github.com/weixu365/serverless-scriptable-plugin#hooks

[weixu365]

The other option is to add Output of the resources, you can reference here: http://www.goingserverless.com/blog/api-gateway-url

[andreimcristof]

@weixu365 you're an absolute rockstar. Thanks!