Known Limitations

Meltano Cloud is currently in Beta.

While in Beta, functionality is not guaranteed and subject to change.
If you're interested in using Meltano Cloud please join our waitlist.

Limitations during Beta #

Manually-submitted schedules lists #

During Beta, Meltano Cloud will only run schedules which you have explicitly declared and requested.

In the future, Meltano Cloud will automatically run any schedules you have configured to run within the named environment.

See related issue: #6853.

Other Unsupported Features in Meltano Cloud #

The following features are not currently scoped for inclusion for the Meltano Cloud GA.

  1. Hosted Airflow as orchestrator
    • At launch, Meltano will not support hosted Airflow orchestration. Instead, Meltano Cloud provides its own built-in managed scheduler and orchestrator.
    • Workaround:
      • We are evaluating options for users to invoke workloads from external services and from the command line. These could provide a method of remote execution from a self-managed Airflow server, for instance.
  2. Hosting of BYO web services and other stateful service backends
    • At launch, Meltano will not allow incoming traffic to any running container. This is for security reasons.
    • Workarounds:
      • We may in the future offer BYO-services when defined as Meltano plugins. Due to the additional security provisions required, this additional functionality may only be available for premium service tiers.
  3. Manipulating state artifacts
    • Although incremental replication is supported in Meltano Cloud, direct state manipulation is not yet supported.
    • In the future, users will be able to, for example, seed initial state by setting Meltano Cloud as a state backend.

Based upon user feedback, we will continue to reevaluate the list of supported and non-supported features for Meltano Cloud. If you have an urgenct need for any of the above features, please let us know!