Altostra Docs

›CLI

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

Configuration files

File structure

Both the configuration file and the parameters-map file share the same simple structure - they are both .json files containing an object where all its properties are strings.

A config file may look like this:

{
  "param1": "value1",
  "param2": "value2"
}

Configuration files

A configuration file is just a mapping from configuration-keys to values. All of which are strings.

Configuration mapping

It is possible for a configuration-set to contain values with configuration keys that differ from the parameters that a project requires. It is also possible for a configuration-set to contain a single value that may be used for several project's parameters.

For these cases, a parameter-mapping file can be used. The parameter-map file is a simple .json file that maps project parameters to configuration-set value keys.

Suppose our example config.json file:

{
  "param1": "value1",
  "param2": "value2"
}

A project that expects the following parameters:

  • param1
  • PARAM_2
  • p2

And that our configuration param2 can satisfy both PARAM_2 and p2.

We can create the following parameter-map file map.json:

{
  "PARAM_2": "param2",
  "p2": "param2"
}

And then deploy, or compile, our project using that file with the --parameter-map option:

$ alto deploy stack-name:version-name \
    --config-set config.json \
    --parameter-map map.json
$ alto compile --config-set config.json --parameter-map map.json
← Scripting optionsAutnentication Required →
  • File structure
  • Configuration files
  • Configuration mapping

Ready to Get Started?

Get Started for Free
© 2022 Altostra, Inc.