serverless-plugin-additional-stacks
serverless-plugin-additional-stacks copied to clipboard
nordcloud
Additional Stacks Plugin for Serverless 1.x
Hi Team, I was trying to deploy my additional stack using the sls deploy additionalstack and encountered the issue to deploy the Type: AWS::Serverless::Application. I have added the Transform: AWS::Serverless-2016-10-31...
Serverless supports loading from multiple configuration files: https://www.serverless.com/framework/docs/providers/aws/guide/variables#multiple-configuration-files Example: ```yml resources: - Resources: ApiGatewayRestApi: Type: AWS::ApiGateway::RestApi - ${file(resources/first-cf-resources.yml)} - ${file(resources/second-cf-resources.yml)} - Outputs: CognitoUserPoolId: Value: Ref: CognitoUserPool ``` However, this does...
Is there a way to put my functions in different stacks? I'm hitting the resource 200 limit. Thanks
As seen in the following pull request on Serverless core: https://github.com/serverless/serverless/pull/5997 When the additional stacks include a `Transform` section (which is used to apply a macro, to allow for additional...
serverless accepts: resources: - ${file(resources/s3-bucket.yml)} This fails with ServerlessError: Template format error: Any Resources member must be an object. Its unpractical to have all definitions in one file
Hi, Imagine I have 2 additional stacks in my project : apiGatewayStack & cognitoStack. My cognitoStack needs apiGateway values in order to be setup. That's why i'm declaring apiGatewayStack before...
If I put a bunch of http handler functions in an additional stack where can I get their urls? Currently the sls info doesn't show anything about the additional stack
If I have functions with http events spread across different stacks. Does each stack expose a different url or would they all share the same url.
This plugin doesn't use the `cfnRole` as specified in the serverless.yml. The expected behavior would be for it to deploy with the `cfnRole` defined in the `provider` section of the...
Would be nice if stack policies could be set inline similar to how it's handled in the serverless.yml file: _stackPolicy: # Optional CF stack policy. The example below allows updates...
