You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, During deployment the parachain team waits until IDHub colleagues perform a test and inform us that everything is okay. Instead we should create a smoke test as part of the deployment process so that we don't have to wait for the feedback from the IDHub colleagues.
we don’t run scripts for parachain pre-checks, but if it helps, these are the manual checks I’ve been running and where usually the issues are spotted:
parachain connects over wss
tee worker is registered
enclave connects over wss
enclave shielding key matches with the one stored in the parachain
they should be easy to integrate in a post-check script., we keep getting the last one wrong
The text was updated successfully, but these errors were encountered:
Context
Currently, During deployment the
parachain
team waits untilIDHub
colleagues perform a test and inform us that everything is okay. Instead we should create a smoke test as part of the deployment process so that we don't have to wait for the feedback from the IDHub colleagues.As mentioned by @jonalvarezz
they should be easy to integrate in a post-check script., we keep getting the last one wrong
The text was updated successfully, but these errors were encountered: