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
{{ message }}
This repository has been archived by the owner on Jul 11, 2023. It is now read-only.
With #122 we have implemented tests on one of our S3 modules. The purpose of this issue is to get those tests hooked up to CI. This requires:
updating .gitlab-ci.yml
define the stages, with linting being the first, and deploying stuff to aws second
define a job in the aws stage that has a manual trigger - it does not run on its own when a new build is run on gitlab.. an operator would need to use the gitlab UI to trigger the job to run. I think this is when
use credentials stored in gitlab secrets for now, we'll probably use vault in the future
The text was updated successfully, but these errors were encountered:
With #122 we have implemented tests on one of our S3 modules. The purpose of this issue is to get those tests hooked up to CI. This requires:
.gitlab-ci.yml
stages
, with linting being the first, and deploying stuff to aws secondwhen
The text was updated successfully, but these errors were encountered: