These are chat archives for truetandem/fedramp-dashboard

28th
Jun 2016
Laura Gehardt
@lauraGgit
Jun 28 2016 14:32

@bmallred so expect in the next rerun an array in the top level ATO-letter called Underlying_CSP_Package_ID.
For reuse calcs they should delineate between directly leverages, and how they are leveraged by other CSPs. (Non-direct leverages will not need to appear in filtered tiles).

I imagine that algorthim for individual CSP reuse would be:
CSPReuse = Leveraged_ATO_Letters.length + sum(Leveraged_ATO_Letters.length where Package_ID in Underlying_CSP_Package_ID)

Laura Gehardt
@lauraGgit
Jun 28 2016 14:46
^ and i can't recommend es6 Array.prototype.filter enough for that latter!
data.filter(csp => csp.Underlying_CSP_Package_ID.includes(Package_ID))
Laura Gehardt
@lauraGgit
Jun 28 2016 15:16
Or more completely:
leveragedATOs = data.filter(csp => csp.Underlying_CSP_Package_ID.includes(Package_ID))
summedReuses = leveragedATOs.map(csp => csp.Leveraged_ATO_Letters.length).reduce( (prev, curr) => prev + curr )
Laura Gehardt
@lauraGgit
Jun 28 2016 16:24
I developed more complete algorithms that take this into account, but checking with FR for clarification
Bryan Allred
@bmallred
Jun 28 2016 16:47
sounds good :)
Bryan Allred
@bmallred
Jun 28 2016 17:55
@lauraGgit: does the verbiage for TG-71 line-up with what you wrote above?
Bryan Allred
@bmallred
Jun 28 2016 19:51
@vzvenyach is there anything we can help out w/ for the S3 deployment(s)?
V David Zvenyach
@vzvenyach
Jun 28 2016 20:00
nope. i actually submitted a PR upstream on something here at 18F that will make this crazy simple
Bryan Allred
@bmallred
Jun 28 2016 20:09
awesome... so once that is applied it be a couple of tweaks in the travis config?
V David Zvenyach
@vzvenyach
Jun 28 2016 20:09
yep. if that even...
i'm working right now on using federalist.18f.gov
which automatically deploys to S3
and all we need to do is point federalist to the repo. and magic autodeploys
assuming this PR 18F/federalist-docker-build#11 gets merged and deployed, I may be able to get this up and running by tomorrow am
John Flores
@floresj
Jun 28 2016 20:10
Will you need us to publish/check-in minified/concatenated resources to our repo?
V David Zvenyach
@vzvenyach
Jun 28 2016 20:11
this is a great question...
i know that the npm run package script works magic
Bryan Allred
@bmallred
Jun 28 2016 20:11
@floresj has the gulp set up for that i think
V David Zvenyach
@vzvenyach
Jun 28 2016 20:11
yep. i used it yesterday locally
it's dope
John Flores
@floresj
Jun 28 2016 20:12
Ok great. No issues?
Bryan Allred
@bmallred
Jun 28 2016 20:12
we just don't add it to the repo during commits atm
V David Zvenyach
@vzvenyach
Jun 28 2016 20:12
makes sense
i'm going to work with the federalist team to see if i can do a deploy script... but it may not work.
Bryan Allred
@bmallred
Jun 28 2016 20:12
good to go
V David Zvenyach
@vzvenyach
Jun 28 2016 20:12
i know that the travis deploy would be easier there
right now, sitting locally is this change to _travis.yml:
deploy:
  provider: s3
  script: "npm run package"
  access_key_id: "YOUR AWS ACCESS KEY"
  secret_access_key: "YOUR AWS SECRET KEY"
  bucket: "S3 Bucket"
  skip_cleanup: true
  local_dir: build
  acl: public_read
but, our S3 access is limited to sandboxes atm
Bryan Allred
@bmallred
Jun 28 2016 20:17
@vzvenyach i may move the task from taiga to a taiga/github issue so it can transcend the sprint backlogs
V David Zvenyach
@vzvenyach
Jun 28 2016 20:17
cool cool
Bryan Allred
@bmallred
Jun 28 2016 20:22
removing TG-98 and moved to #5 in github or TG-99 in taiga