Skip to content

Cloud provider split #14

@macebalp

Description

@macebalp

Description:
Using cloud id to communicate with Akeyless is great, it removes the need to store credentials to access it. Using this package has a downside though, it depends on many providers libraries (AWS, google-cloud, Azure) even though we only need it for AWS in our case. This causes that our Lambda zip deployment jumps from 800K to 8MBs.

Request:

  • Have separate packages for each provider
  • Or, have a require specific in each provider's method so unnecessary providers can be excluded. For instance: changing providers dependencies to peer Dependencies so we can skip installing unneeded ones (ignoring warnings) or install unnecessary ones a dev Dependencies so they are not shipped with the package

Best.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions