aws-extensions-for-dotnet-cli
aws-extensions-for-dotnet-cli copied to clipboard
aws
Extensions to the dotnet CLI to simplify the process of building and publishing .NET Core applications to AWS services
### Describe the bug I will preface this by saying this could be a GitLab pipeline issue, however, I have also seen this happen on a local development machine. Command:...
### Describe the feature Extend supported syntax for defining "template-parameters" in serverless template configuration JSON files to include object and array syntax. ### Use Case If deploying a serverless template...
Our company policy is that code deployments must be uploaded to a specific S3 bucket, which enforces encryption. In our dev account, we occasionally deploy lambdas and stacks via the...
### Describe the feature This came up during discussion of https://github.com/aws/aws-extensions-for-dotnet-cli/issues/247. We need to check if in later versions of .NET Core SDK(s), ZIP compression library maintains Linux file permissions....
### Describe the feature This may be more a pertinent to using SAM template's `AutoPublishAlias` or `SemanticVersion` rather than dotnet CLI, but deployment creates several artifacts in the S3 deployment...
### Describe the bug According to [AWS docs for SAM-style _StateMachine_ declaration](https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/sam-resource-statemachine.html#sam-statemachine-definitionuri), the `DefinitionUri` should support specifying a local file path. However, in practice deployment fails. ### Expected Behavior Given...
### Describe the feature We would like the ability to set the folder path (relative to the current project folder) that the publish tool uses, instead of it being hard-coded...
**Setting CodeUri in the Globals section of the SAM template zips up the current working directory.** **Workaround:** Don't put CodeUri in Globals, and leave it in the individual function specifications....
