Skip to content

Repository files navigation

DevOps Challenge - Darrell Shack

JavaScript Style Guide

Hello All,

Welcome to my DevOps Challenge, below are the steps for the CI/CD process:

  1. Our CI/CI uses git actions to trigger workflow depending on pushes/merges to different branches within our repo. I have two branches, one is our main branch and the other is a feature.

  2. When you add any commits or branches to our repo, it kicks off a linter and test. For our use case, we use the following yml files to check for dependencies and linting/testing:

  • code_quality_super-linter
  • dependency_security_scan
  • npm-commit_ci
  1. Once we check for the quality of code and dependencies, we can merge this into our main branch whiches kicks off our deployment/mutant testing with the following yml files:
  • mutant_testing_tool
  • npm-publish-deploy

Bonus

  1. I attempted to add the function User as a lambda and the lambda based on the documentation will inherit some of the properties of the provider. (EX runtime)

  2. Next, within the resource, I deployed an RDS instance based on Cloudformation syntax which would provide us with the connection string.

  3. Once the resource is deployed, I added an output section within the template to capture the connection string of the RDS resource. I use this to reference an output that can be called from within the template

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

Packages

Used by

Contributors

Languages