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
The purpose of this flag is not to start Forest services and exit as soon as basic initialisation is completed. This will open some possibilities, amongst others:
testing initialisation logic via component tests, like creating the keystore,
getting the JWT token easily.
The exit should happen before the snapshot download. It may make sense to move the snapshot download as far as possible to allow the initialisation of as many objects as possible
Task summary
introduce the --exit-after-init flag to the Forest daemon,
shuffle the code around so that as many initialisations take place as possible
write a component test where Forest successfully goes through initialisation ⚠️ make sure that during the tests a temporary data dir is used - we don't want to override the default keystore by running tests.
Acceptance Criteria
The flag is implemented and the tests are passing, including the new ones,
The flag is appropriately documented, and the changelog is updated,
By default, the value of the flag is false,
Other information and links
The text was updated successfully, but these errors were encountered:
Issue summary
The name of the flag could be improved. :)
The purpose of this flag is not to start Forest services and exit as soon as basic initialisation is completed. This will open some possibilities, amongst others:
The exit should happen before the snapshot download. It may make sense to move the snapshot download as far as possible to allow the initialisation of as many objects as possible
Task summary
--exit-after-init
flag to the Forest daemon,Acceptance Criteria
Other information and links
The text was updated successfully, but these errors were encountered: