Skip to content

Project Meeting September 2021

Jump to bottom
programmer2coder edited this page Sep 2, 2021 · 2 revisions

Present: Jess L, Samantha S (recording), Cori O, Emily H, Eileen K, Michael B, Paul P Regrets: Junette T, Aaron C

Go around: share something data gen-y

  • Jess: focused on other projects! cheering on github progress!
  • Emily: working through Trailhead on CCI
  • Paul: working on support and enablement Snowfakery (internal webinars); some big customers are starting to use it!
  • Eileen: made edits in Github for Read Me file in Data Gen Toolkit repo, working through Trailhead on CCI
  • Cori: cheerleader, sharing information with other teams, promoting upcoming Sprints
  • Andrew and Michael: How to pull recipe notes into other documentation?
  • Michael: stirring the pot with algorithm for generating fake email addresses; submitted recipe for
  • Jung: using new Snowfakery VF plugin library and encountered an error (bug?); order of insert logic for Snowfakery, encountered weird behavior with loading Campaign Members w/o "friend" feature (Paul mentioned there is another workaround available)
  • Sam: YAY we moved repos! Also, planning to use Snowfakery to load dev org for personal open source Conga Composer project (stay tuned!)

Snowfakery order of insert

  • Snowfakery reads recipes and loads data in order of dependency
  • Jung might have found a bug
  • There is a way to override the inferred load order

Protocol for Testing Snowfakery Recipes

  • Layer 1: Ensuring that recipes run (not just on your computer) (can be handled through Github Actions that run after Commit)
  • Layer 2: Snowfakery ran properly, but the resulting data do not make sense (ie 10 members per household is unexpected result)
    • we should consider that this is a process
    • Robot or Python can assert that the right number of records were creates
    • do the dates make sense for Recurring Donations? do the picklist values make sense?
    • do testers need special knowledge?
  • Layer 3: Post-install steps (what happens after a recipe is run?)
    • ex: running reports
    • ex: pivot tables in excel
    • ex: Fund X cannot have payments for certain dates
  • Checklist of things before merge
  • Are there limits to Github Actions?
  • At what point would we encounter Dev Hub limits?
  • What about Robot Script (CCI)
  • Idea: poke around a Salesforce UI and test recipes (compatible with different volunteer strengths)
  • Idea: combine Scratch Org + NPSP data model + data load (all in one CCI Flow) and then Robot can happen at the end
  • Idea: configure Github Actions as a sprint project

Gathering feedback on CCI Trail

  • What's the preferred format?
  • Cori's recommendation: post in CCI group in the Power of Us Hub or the CCI group in the Trailblazer Community
  • if there are typos in the Trailhead content, report it thru the Trailhead link
  • Samantha happy to help craft a post if you aren't sure what to write or feel intimiated
  • most of the people who answer those questions are friendly and named David

upcoming Open Source Commons Events

  • Sprint AMER Oct 20-21 (save the date!)
  • Show and Tell talk Sept 29 @ 9 am Pacific / 12 Eastern (30 mins to describe project, aim for evergreen content)

Celebrate:

  • Thanks to Medium article, Frontier Scale Team has assigned a Product Manager to Snowfakery
  • moving recipes to Snowfakery Recipes dedicated Github repo

Upcoming Events:

  • Meeting in a Box presentation: Sept 8 w DC
  • Generating Data with Flow presentation w Automation Hour: Sept 17
  • Meeting in a Box presentation: Oct 19th w Seattle/Bellingham
  • Meeting in a Box presentation: Jan 12 w San Fran nonprofit UG

Questions to keep in mind for presentations:

Clone this wiki locally