v0.0.8

v0.0.8, February 19, 2024

⚠️ Deprecations

N/A

🚀 Performance improvements

N/A

✨ Enhancements

Additional protocols for EC2

• Previously, Alto managed EC2 instances only via the SSH / SCP protocol. Now, users can specify whether they want to use Amazon Systems Manager to manage their instance. You can learn more AWS Systems Manager here.
• This can be controlled via the protocol key within an EC2 agent's infra configuration.

Enhanced logging

• Starting in v0.0.7, Alto uses Textualize/rich to create beautiful, highly readable logs in Terminal. By default, these logs show a condensed version of events. To view all log events, users can use the --verbose CLI argument.

🐞 Bug fixes

N/A

📖 Documentation

• Updated the IAM policy documents associated with the ssh protocol, and added a policy document for the ssm protocol.
• infra section is now its own group with separate pages for each infrastructure type.

🛠️ Other improvements

Updated naming conventions in Agent configuration

• additional_paths --> mounts
• download_files --> artifacts

requires_dependency() utility

• This function prompts the user to download Alto extensions when certain modules do not exist — e.g., if the user wants to use a Docker but hasn't installed the necessary modules, Alto will prompt them to install alto-dev[docker].

v0.0.7

v0.0.7, January 30, 2024

New features

--verbose flag
Previously, Alto would log all events from every stage of the infrastructure build and entrypoint execution. Now, users by default get a condensed version of the console events and can use --verbose to see all log events.

Improvements

N/A

Bug fixes

Fixed template from alto init
Updated the bootstrap_actions key in the template created by alto init to post_build_cmds

v0.0.6

v0.0.6, January 26, 2024

New features

N/A

Improvements

N/A

Bug fixes

Fixed import errors
In previous versions of Alto, users would need to install all of Alto's extras to use any Alto functionality. In this version, imports are separated so that extras are only imported if they are needed.

v0.0.5

v0.0.5, December 28, 2023

New features

Docker image support

• In previous versions of Nomad, users could only run their code on the agent's runtime environment itself. In this version, users can run their code in a Docker image inside the agent. They can do so with the image key:

my_agent_name:
  infra:
    - type: ec2
    ...
  image:
    type: docker
    base: python:3.10.8-slim-bullseye
    registry: dockerhub
    registry_creds:
      username: ...
      password: ...
  requirements: ...
...

The image key accepts the following nested keys:

• type: this represents the image type. As of now, only type docker is supported
• base: Nomad automatically builds your Dockerfile and Docker image for you based on your configuration file. This key specifies the base image upon which to build.
• context: this key is used to specify a pre-existing Dockerfile that you wish to run on your agent. Note that, if you specify this key, Nomad will not build a Dockerfile for you. In other words, this and base are mutually exclusive.
• registry: the registry to which to push the completed image. As of now, accepted values are dockerhub and ecr. If this isn't specified, Nomad defaults to ecr.
• registry_creds: a dictionary of the registry login credentials. This is optional — Nomad will prompt you if it needs login credentials to push your image to the desired registry.

Improvements

None.

Bug fixes

None.