Skip to content

[package.metadata.lambda.deploy] isn't respected if binary-name is used #866

@nemosupremo

Description

@nemosupremo

Cargo.toml

[package]
name = "mybin"

[package.metadata.lambda.deploy]
memory = 512
timeout = 60

Without binary-name

$cargo lambda deploy \                                                       
            --dry \                 
            mybin        
🔍 deployment for function `mybin`:
🏠 zip file located at /Users/nemo/mybin/target/lambda/mybin/bootstrap.zip
🛠️  binary last compiled 12 minutes ago
🏗️  architecture arm64
🗃️  files included in the zip file:
  - bootstrap
🛫  AWS SDK configuration:
  - region: us-east-2
🍿 function configuration:
  - timeout: Some(Timeout(60))
  - memory: Some(Memory(512))
  - enable_function_url: false
  - disable_function_url: false
  - tracing: None
  - role: None
  - layer: None
  - runtime: "provided.al2023"
  - env_options: None

With binary-name

$ cargo lambda deploy \
            --binary-name mybin \
            --dry \ 
            mybin-lambda
🔍 deployment for function `mybin`:
🏠 zip file located at /Users/nemo/mybin/target/lambda/mybin/bootstrap.zip
🛠️  binary last compiled 14 minutes ago
🏗️  architecture arm64
🗃️  files included in the zip file:
  - bootstrap
🛫  AWS SDK configuration:
  - region: us-east-2
🍿 function configuration:
  - timeout: None
  - memory: None
  - enable_function_url: false
  - disable_function_url: false
  - tracing: None
  - role: None
  - layer: None
  - runtime: "provided.al2023"
  - env_options: {} 

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions