Skip to content
New issue

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

Feature | Implement GitOps with GitHub Actions for Ref Arch #519

Open
exequielrafaela opened this issue Jun 20, 2023 · 0 comments
Open
Assignees

Comments

@exequielrafaela
Copy link
Member

exequielrafaela commented Jun 20, 2023

Describe the Feature

Expected Behavior

Once implemented, the Reference Architecture should support GitOps using GitHub Actions. This would allow for more streamlined and automated deployment workflows.

Use Case

This feature is valuable for improving the efficiency and reliability of deployment workflows. It would be particularly useful for client projects that require this feature.

Describe Ideal Solution

The ideal solution would involve integrating GitHub Actions into the Reference Architecture to support GitOps workflows.

An alternative could be to use the Atlantis AWS module, which appears to be widely adopted and solid. This module includes a practical example for the Reference Architecture of ECS Fargate, including VPC, SSL certificate using ACM, ALB, Domain name using AWS Route53, AWS ECS and AWS Fargate running Atlantis Docker image, and AWS Parameter Store for secrets management.

Alternatives Considered

An alternative could be to continue without GitOps support, relying on existing manual deployment workflows. However, this could lead to inefficiencies and potential errors.

Additional Context

This feature request arose from a discussion about improving deployment workflows and efficiency. The addition of GitOps support using GitHub Actions was suggested as a potential solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants