Skip to content

Instantly share code, notes, and snippets.

@notmarkmiranda
Last active March 8, 2024 02:39
Show Gist options
  • Save notmarkmiranda/6d514ebf474f60052d0e479c8fc280d1 to your computer and use it in GitHub Desktop.
Save notmarkmiranda/6d514ebf474f60052d0e479c8fc280d1 to your computer and use it in GitHub Desktop.
SS Brag Doc.md
gists
id url createdAt updatedAt filename isPublic
6d514ebf474f60052d0e479c8fc280d1
2024-01-17T01:05:19Z
2024-03-08T02:06:42Z
SS Brag Doc.md
false

Week ending 2024-MAR-10 | Week 10

  • Working on Feature - xxxx for adding abstraction layer to blueprint model for accessing settings from config_parser
  • Studying for AWS Solutions Architect exam

Week ending 03-MAR-2024 | Week 9

  • Passed AWS CCP Exam on 29-FEB-2024
  • merged Bug - 2745 on group_by exceptions in mgl_sheet
    • this was a failure on reloading sheets inline in mgl_config_sheet
    • the fix is to change that when the sheet reloads then verify the reload was successful before moving on.

Week ending 25-FEB-2024 | Week 8

  • Short week, I took Tuesday off for family things
  • Pairing with [[Megan Maple]] on her ticket
  • Pairing with [[Isaac Tobler]] on abstract logic for finding / building Blueprint from config_sheet
  • Merged UI data abstraction for program config
  • Working on (2745) exceptions around a call to group_by after a sheet is updated in line twice. Refactoring the methods to be have more error handling.
  • Studying for AWS Certified Cloud Practitioner exam.

Week ending 18-FEB-2024 | Week 7

  • Finished Bug - 2468
    • a lot of the hold up was because of not being able to run control-center-project-provisioning locally
    • in order to test this
      1. i had to push an MR
      2. run a job to publish a draft version of the MR
      3. update scc to referenced that published version
      4. ssh and docker exec into the box and run yarn
      5. restart the containers
      6. and hope for the best
    • i learned to deploy to MARS2
      1. updating the ss to indicate that i was using it
      2. add the deploy-to-mars2 tag to the MR
      3. push a blank commit
  • Paired with Isaac on 2768 - Add abstraction layer to ProgramConfig for UI Data

Week ending 11-FEB-2024 | Week 6

  • Continuing Bug - 2468 - Bug: Disable next button in manual provisioning
  • Config Service digging with [[Isaac Tobler]]

Week ending 04-FEB-2024 | Week 5

  • Bug - 2734 - Delete row being called with no sheet id
    • Pushed the MR and addressed feedback
  • Bug - 2468 - Bug: Disable next button in manual provisioning

Week ending 21-JAN-2024 | Week 3

  • Bug - 1845 - Malformed / Unescaped Blueprint names sent through POST /apps endpoint to Portfolio Workapps are causing navigation to unexpected or nonexistent routes
    • Approach: Without full context of where the malformed data is coming from, it just seems that the body params are the only culprit. Running it up the flagpole through code review, specifially from [[Kesha Veniaminov]] & [[Dillon Byron]].
    • MR: https://git.lab.smartsheet.com/control-center-dev-team/smartsheet_controlcenter/-/merge_requests/2088
    • Conversation with [[Ian Phillips]] about how this is not a PB bug and should be on the workapps team. Meeting with [[Ian Phillips]] & [[Dillon Byron]] and discovered this is no longer an issue
  • Rubocop Work
    • working on Style violations
  • Config Service phase 1
    • [[Config Service Sync]]
    • divide & conquer for figuring out where things are being accessed and how we can abstract ConfigParser out. Week ending 28-JAN-2024 | Week 4
  • Bug - 2734 - # Delete row being called with no sheet id
    • logs show response message of Requested URL does not support this method: DELETE
    • the URL being hit is /sheets//rows?ids=1149311733720964
      • double // means the id is not being interpolated in
    • learned about the board_logs database table to check for provisioning status
  • Escalation questions for Jayoung - [[Smartsheet On-call documentation]]?
    • There were some escalations over the weekend that you did not acknowledge, how do you know when you should and shouldn't acknowledge and deal with an escalation?
  • Config Service phase 1
    • working through spreadsheet of existing calls to ConfigParser.new to understand what and how this is being used.

#smartsheet #careergoals

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment