Open RothAndrew opened 1 year ago
A likely good option here is to use GitHub Actions as the trigger. The workflow that gets run can live in the same repo that stores the Infrastructure as Code that we use to establish the persistent resources in that account:
AFAIK that repo doesn't exist yet, but we should make one and do the above resources as IaC once we get access the UDS Ephemeral CI AWS Account. CC @Vandiver247
This all sounds good though. Running at 0400 EST on weekdays is fine as well, noting that we're hoping to do nightly (at midnight EST) runs of our EKS CI jobs
Design for this issue is specified here: https://github.com/defenseunicorns/uds-aws-account-iac/issues/3
@UncleGedd please review. Once this design gets refined/reviewed/accepted, I will start implementation.
Commenting here for posterity: deferring to @zachariahmiller on this one, thanks!
Met up with @zachariahmiller and got a good way forward. Getting started on implementing this.
@Vandiver247 when do you anticipate the AWS account will be ready for us to start working in?
As a maintainer of UDS projects that needs to use an AWS account for CI, I want any orphaned resources to be periodically deleted, so that their CI runs do not run into LimitExceeded errors.
As the company that supports UDS projects that needs to use an AWS account for CI, we want any orphaned resources to be periodically deleted, so that we can avoid wasting money on unneeded and unused resources.
Acceptance Criteria:
Notes:
before 4am every weekday
but it isn't yet clear which timezone it used. Using 2AM Eastern Time should avoid conflicts with Renovate regardless of which timezone Renovate uses.