Skip to content
This repository has been archived by the owner on Jul 11, 2023. It is now read-only.

setup CI to run tests on S3 full access policy module #144

Closed
ketzacoatl opened this issue May 21, 2018 · 2 comments
Closed

setup CI to run tests on S3 full access policy module #144

ketzacoatl opened this issue May 21, 2018 · 2 comments

Comments

@ketzacoatl
Copy link
Contributor

ketzacoatl commented May 21, 2018

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
@mcgirr
Copy link
Contributor

mcgirr commented May 26, 2018

I'm currently working on this under the ci-s3-full-access-policy-module branch.

The current CI output (still a WIP) is available on the gitlab mirror pipeline for that branch.

@mcgirr
Copy link
Contributor

mcgirr commented Oct 27, 2020

Closing this issue since it sounds like plan is to eventually shift all the CI for the repo to a Github Workflow as part of changes like #320

@mcgirr mcgirr closed this as completed Oct 27, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants