You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: