We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi, We have a deployment model that uses aws ec2 built as immutable instances of Amster. So the config such as Journeys being static, we do
Version control the artifacts identified as such and use it to build the EC2 AMIs to create the autoscaled cluster.
Is there a way frodo can support the above usecase by creating exports compatible with amster, so it can minimize the development pain point?
Please advise if there is an more optimized way to do this.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi,
We have a deployment model that uses aws ec2 built as immutable instances of Amster. So the config such as Journeys being static, we do
Version control the artifacts identified as such and use it to build the EC2 AMIs to create the autoscaled cluster.
Is there a way frodo can support the above usecase by creating exports compatible with amster, so it can minimize the development pain point?
Please advise if there is an more optimized way to do this.
The text was updated successfully, but these errors were encountered: