Altostra Docs

›Commands

Getting Started

  • Welcome to Altostra
  • Connect your accounts
  • Install the developer tools
  • Log in from the CLI

Tutorials

  • Create a Static Website
  • Create a Scalable Webhook
  • Create a Simple API Project
  • CI/CD with Altostra CLI and Github Actions
  • Deploying a Project to Multiple Environments

How To

    Working with projects

    • Create a new project
    • Deploy a project
    • Manage a project

    Working with environments

    • Manage an environment
    • Configure stacks expiration for an environment

    Working with the Editor

    • Grant access to vendor services
    • Use the Parameter Store
    • Use a custom CloudFormation resource
    • Attach a custom policy to a Function
    • Connect a Function to VPC
    • Add filter policy to SNS subscription

    Organization account settings

    • Set General Settings
    • Connect a Git account
    • Connect Cloud Accounts
    • Manage log aggregation accounts

CLI

  • Altostra CLI
  • Commands

    • account
    • activity-log
    • api-key
    • build
    • config
    • console
    • deploy
    • docs
    • endpoints
    • environments
    • import
    • init
    • invalidate
    • login
    • logout
    • new
    • projects
    • push
    • deploy-cfn
    • deploy-sam
    • deploy-sls
    • stacks
    • sync
    • tasks
    • templates
    • versions
    • whoami

    Options

    • --debug
    • --verbose
    • Scripting options
  • Configuration files

Errors And Solutions

  • Autnentication Required

Technical Reference

  • Environments
  • Stacks
  • Projects
  • Versions Repository
  • Log Shipping
  • Deployment Modes
  • Altostra Cloud Integration

Integrations

    CI/CD

    • CircleCI

    Git

    • Git integration
    • Connect a GitHub account
    • Connect a Bitbucket account

    Messaging

    • Connect a Slack workspace

    Security

    • Connect an Auth0 tenant

build

Build an Altostra project and save as SAM template to sam-template.json.

$ alto build

Options

--environment

The environment to use for configuration values during compilation.

Aliases: --env

Required: no

--config-set <config-file>

Specify a file with additional configuration values to use during compilation.

Aliases: --cs

Required: no

--parameter-map <map-file>

Specify a file with parameter-mappings to use during compilation.

Aliases: --pm

Required: no

--project-path

Specify project directory. If not specified, project directory is assumed to be the current directory.

Aliases: --pp

Required: no

--format

Select either json or yaml as the template format. Default: json

Aliases: --fmt

Required: no

--ignore-missing-params

If set, all missing configuration values for parameters are ignored. Otherwise, you must provide configuration values for all parameters.

Required: no

Providing configuration

If a project has parameters - they all must be satisfied with configuration values from configuration-sets attached to an environment or provided by the --config-set option.

To remove this restriction and ignore any missing values for parameters, set the --ignore-missing-params option:

$ alto build --ignore-missing-params

Configuration values can be provided in two ways (which are not mutually exclusive):

  1. Specify a configuration-set file using the --config-set option
  2. Specify an environment using the --environment option

If you use both these options together, the keys from the configuration file will take precedence over the configuration sets in the environment.

$ alto build --config-set config.json --environment Production

Parameters mapping

A parameters-map file may be used to map between parameter-names expected by the project, and the provided key in the configuration-set.

← api-keyconfig →
  • Options
    • --environment
    • --config-set <config-file>
    • --parameter-map <map-file>
    • --project-path
    • --format
    • --ignore-missing-params
  • Providing configuration
    • Parameters mapping

Ready to Get Started?

Get Started for Free
© 2022 Altostra, Inc.