RichardOrnelas

# ECS Execution
resource "aws_iam_role" "ecs_execution" {
  name               = "${var.project}-${terraform.workspace}-ecs-execution"
  assume_role_policy = data.aws_iam_policy_document.ecs_execution_grant.json
  description        = "${var.project} ECS Task Execution Role"
}

resource "aws_iam_role_policy" "ecs_execution_policy" {
  name   = "${var.project}-${terraform.workspace}-ecs-execution-policy"
  role   = aws_iam_role.ecs_execution.id

RichardOrnelas

Fees v0 Tech Spec

References

https://developer.authorize.net/api/reference/index.html

Summary

Track and charge fees to borrowers via the Borrower Portal. We will leverage Authorize.net as a partner for the charging of the credit and settlement of the money into our merchant account.

Technical Questions

1. Integration in with Auth.net should live in the Backend, Fronted, or Both ? Lean toward FE for keeping credit info out of backend.

RichardOrnelas

# frozen_string_literal: true

namespace :generate do
  desc "create blueprint for each loan entity"
  task graphql_attributes: :environment do
    # include the GeneratorHelpers
    include GeneratorHelpers

    # Types to be generated after looping through the models
    new_union_types = {

RichardOrnelas

Models

Users

• Relationships
  • has_many :assignments, class_name: "Loan"
  • belongs_to :branch <-- do they?
    • Tracks Session IDs
• Attributes
  • first_name
  • last_name

RichardOrnelas

Keybase proof

I hereby claim:

• I am richardornelas on github.
• I am richardornelas (https://keybase.io/richardornelas) on keybase.
• I have a public key whose fingerprint is 576C 51CE D6BD 0DA5 834D A01E 2FAE 1C1B 8869 8AC1

To claim this, I am signing this object: