
Product
Introducing Socket Firewall Enterprise: Flexible, Configurable Protection for Modern Package Ecosystems
Socket Firewall Enterprise is now available with flexible deployment, configurable policies, and expanded language support.
@slsplus/template
Advanced tools
This component is used behind the scenes to deploy your YAML templates. It is loaded by the serverless CLI and executed just as any other component. However, there's a lot you can do with this component programmatically. See the sections below for some ex
This component is used behind the scenes to deploy your YAML templates. It is loaded by the serverless CLI and executed just as any other component. However, there's a lot you can do with this component programmatically. See the sections below for some examples.
To deploy to multiple environments you must utilize the programmatic API, via serverless.js file.
serverless.js
const { Component } = require('@slsplus/core')
class Deploy extends Component {
async default(inputs = {}) {
const { env } = inputs
const template = await this.load('@serverless/template', env)
return await template({ template: __dirname + '/serverless.yml' })
}
async remove(inputs = {}) {
const { env } = inputs
const template = await this.load('@serverless/template', env)
await template.remove(inputs)
}
}
module.exports = Deploy
serverless.yml
name: test
lambda:
component: '@serverless/function'
inputs:
name: my-function
description: My Serverless Function
memory: 128
timeout: 20
code: './code'
hanlder": 'handler.handler'
region: us-east-1
runtime: nodejs10.x
Invoking sls --env=dev will result in state files in .serverless/ being prefixed with the value of your env:
Deploy.dev.json, etc. That way you can deploy unlimited environments, add pre/post processing, load whatever .env you need, etc.
A template itself does not contain any methods so custom methods are executed on the specific template aliases.
sls install --component lambda will load the lambda alias from your template, instantiate the corresponding component, and execute the install method passing in the inputs you specify via CLI parameters.
Inputs from the template itself are not passed as they can not be interpreted/resolved without running the entire template.
You can pass as many --component parameters as you need.
serverless.js
const { Component } = require('@slsplus/core')
class Deploy extends Component {
/* ...skipped default method for brevity ... */
async install(inputs = {}) {
const template = await this.load('@serverless/template')
await template.install({ template: __dirname + '/serverless.yml', ...inputs })
}
}
module.exports = Deploy
When invoking methods on a template instance, you always need to pass in a path to the template file or a template object.
Running sls install --component lambda --debug - this will load the template, find the lambda alias, and invoke the install method on the instance of the component.
Visit our github and file an issue with as much info as possible about your problem. If you think you've found a bug - please do post a complete reproduction repo. It will help us and our contributors to help you much faster.
FAQs
This component is used behind the scenes to deploy your YAML templates. It is loaded by the serverless CLI and executed just as any other component. However, there's a lot you can do with this component programmatically. See the sections below for some ex
We found that @slsplus/template demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Product
Socket Firewall Enterprise is now available with flexible deployment, configurable policies, and expanded language support.

Security News
Open source dashboard CNAPulse tracks CVE Numbering Authorities’ publishing activity, highlighting trends and transparency across the CVE ecosystem.

Product
Detect malware, unsafe data flows, and license issues in GitHub Actions with Socket’s new workflow scanning support.