This is a legacy platform changelog. The information reflected here may not represent current functionality and some links may be broken.
We have introduced a new flag (--private-key-file) and an improved error message in the meroxa resources create command with the latest Meroxa CLI release v2.18.0.
This is a legacy platform changelog. The information reflected here may not represent current functionality and some links may be broken.
We鈥檝e introduced improved error messages for out of sync fixture data and unreachable resources, and we've introduced a convenience function to the apps commands to open the dashboard from the CLI with the latest Meroxa CLI release v2.17.0.
This is a legacy platform changelog. The information reflected here may not represent current functionality and some links may be broken.
We鈥檝e introduced an expanded list of Resources in the dashboard experience. In addition to adding new Resources, customers can opt-in to participate in Developer Previews for upcoming Resources in development. And a recent Meroxa CLI release v2.15.0 introduces updated output for meroxa resources list --types which now includes additional information on resource types.
This is a legacy platform changelog. The information reflected here may not represent current functionality and some links may be broken.
Apache Kafka is now available as a resource in Meroxa as a source or destination.
This is a legacy platform changelog. The information reflected here may not represent current functionality and some links may be broken.
Starting today, a public beta of the Microsoft SQL Server resource is available to all customers. Microsoft SQL Server resources can be provisioned in the typical manner in the dashboard or via the CLI:
$ meroxa resources create sourcedb --type sqlserver -u sqlserver://username:password@hostname:1433/dbname
For more information on the Microsoft SQL Server resource, please see the documentation). For any questions or comments, please feel free to email us at [email protected].
This is a legacy platform changelog. The information reflected here may not represent current functionality and some links may be broken.
In situations where your database doesn't have a public IP adresss, a typical pattern of accessing the database from the public Internet is using a bastion host and creating an SSH tunnel to reach it. The ability to create SSH Tunnels between Meroxa and your private databases is now in beta to all customers and is available as a configuration option on all resources.
For more information, please see the SSH Tunnel documentation. For
any questions or comments, please feel free to email us at [email protected].