AssemblyLift
HomeRepo
v0.3
v0.3
  • Welcome to AssemblyLift
  • Learn AssemblyLift
    • Getting Started
    • Services
      • Functions
      • Authorizers
      • IOmod Dependencies
    • Functions
      • Rust Functions
    • IO Modules
      • Registry
    • User Terraform
    • Providers
    • How to Build
    • How to Deploy
  • Development
    • Design Pillars
  • Resources
    • The Lexicon
    • Tutorial: Build a "todo list" backend with AssemblyLift
Powered by GitBook
On this page

Was this helpful?

  1. Learn AssemblyLift
  2. Services

IOmod Dependencies

Defining a dependency on an IO Module

PreviousAuthorizersNextFunctions

Last updated 3 years ago

Was this helpful?

IO Modules (IOmods) are defined in the iomod.dependencies table within the service manifest.

service.toml
[iomod.dependencies.s3]
coordinates = "akkoro.aws.s3"
version = "0.1.0"

IOmods are defined by coordinates in the format organization.namespace.name and a . Occasionally these will be seen written together in the format org.namespace.name@major.minor.patch .

By default IOmods will be fetched from the public at registry.assemblylift.akkoro.io. IOmod binaries can also be loaded from a local path, however this is intended for IOmod development.

[iomod.dependencies.s3]
coordinates = "akkoro.aws.s3"
version = "0.1.0"
type = "file"
from = "/absolute/path/to/executable"

Further details on IO Modules can be found in its .

semantic version
IO Module registry
dedicated chapter