Meshery Build and Release call (24th Aug 2023)

Meshery
1

August 24th, 2023

Attendees:

  • Pranav Singh, Mario Arriaga, Philip Obiora, Saurabh K Singh, Vaibhav Malik, Senali Dilumika, Swastik Gour, Roshan Goswami, Karthik Ayangar

Standing Agenda:

Topics:

  • [Vaibhav Malik] Email on failure job fix #8578
  • [Freedisch] Observability for Meshery Playground
  • [Suhail]
  • [Philip] mesheryctl unit testing
  • [Philip/Ashu] Fix for code coverage reporting
  • [Call For Volunteers]
    • Failing: Deploy CNCF Playground / Update Meshery on CNCF playground link
    • Failing End-to-End tests for Meshery Adapters link
  • [Pranav] Fix mesheryctl release issue#8515 PR#8518
  • [Freedisch/Pranav] Components Definitions
  • [Senali] Meshmap-snapshot for meshery.io link
  • [Mario] [CI] Disable Cypress e2e tests #8543
2

@Yash_Sharma we referenced your MeshMap Snapshot docs on today’s call. :+1:

3

Hopefully, @ash-kamrip or Vaibhav Malik will be able to identify a generic method for preventing meshmap snapshot from running on any forked repos.

4

I think so, is there a github issue referencing this item?

5

@VaibhavMalik4187 please create one.

6

Done. Here’s the link:

1 Like
7

@Lee , I’m not sure if that’s entirely possible. a owner of the forked repo would always have full access to the workflows, even if we define a step such a step , it can always be removed/commented out in the fork.

Could you provide more details as to why we don’t want the meshmap snapshot to run in forked repos ?

8

@ash-kamrip, for my part, I don’t mind in the least if the Snapchat runs in forked repos. That would be just fine. In order for the Snapchat workflow to run, it does require user-specific secrets to be available. So, users that fork the repo will need to supply their own secrets. If memory serves, this would simply be the user’s API token from Layer5 Cloud.

1 Like