Verify that the current deployed pre-release version under the next tag in npmjs is working properly. Maintainers with commit access to the repository can publish a release by merging into the release branch. Once a contributed PR (or multiple PRs) have been merged into master, there is need to publish a production release, after we are sure that the release is stable.
#NPM SERVERLESS STACK OUTPUT INSTALL#
Npm install -save-dev a Production Release (Maintainers) Test your deployed version by installing with the next tag.Once the PR is approved and merged into master, travis-ci will automatically tag the version you created and deploy to npmjs under the next tag.Don't forget to commit the files modified by npm run release (we have the auto-commit option disabled by default).Examine the CHANGELOG.md and update if still required.Update the release notes at CHANGELOG.md and bump the version by running:.Make sure to use conventional commit messages as specified at. To help updating the CHANGELOG.md file, we use standard-version.Once ready, open a PR to contribute your code.
#NPM SERVERLESS STACK OUTPUT HOW TO#
Based on the feedback in the issue, you should be able to plan how to implement your PR. Describe in the issue what you want you plan to implement/fix. Before opening a PR it is best to first open an issue.ContributingĬontributions are welcome and appreciated. You can set permissionsBoundary for all roles with iamGlobalPermissionsBoundary in custom: custom: serverless-iam-roles-per-function: iamGlobalPermissionsBoundary: !Sub arn:aws:iam::xxxx:policy/permissions-boundary-policyįor more information, see Permissions Boundaries. PermissionsBoundaryĭefine iamPermissionsBoundary definitions at the function level: functions: func1: handler: handler.get iamPermissionsBoundary: !Sub arn:aws:iam::xxxxx:policy/your_permissions_boundary_policy iamRoleStatementsName: my-custom-role-name iamRoleStatements: - Effect: "Allow" Action: - sqs:* Resource: "*". Usageĭefine iamRoleStatements definitions at the function level: functions: func1: handler: handler.get iamRoleStatementsName: my-custom-role-name #optional custom role name setting instead of the default generated one iamRoleStatements: - Effect: "Allow" Action: - dynamodb:GetItem Resource: "arn:aws:dynamodb:$:*:table/mytable". Note: Node 6.10 or higher runtime required. Or if you want to try out the next upcoming version: npm install -save-dev the plugin to serverless.yml: plugins: - serverless-iam-roles-per-function Installation npm install -save-dev serverless-iam-roles-per-function A Serverless plugin to easily define IAM roles per function via the use of iamRoleStatements at the function definition block.
0 kommentar(er)
