Deploy challenge info to frontend #81
Open
detjensrobert wants to merge 27 commits into
Open
Conversation
detjensrobert
commented
Feb 7, 2026
detjensrobert
force-pushed
the
dr/frontend-push
branch
3 times, most recently
from
February 11, 2026 06:58
b8028e4 to
e0dc239
Compare
Signed-off-by: Robert Detjens <github@detjens.dev>
Signed-off-by: Robert Detjens <github@detjens.dev>
Replaces the temporary challenge info markdown output. This currently doesn't print out the response from frontend. Signed-off-by: Robert Detjens <github@detjens.dev>
Signed-off-by: Robert Detjens <github@detjens.dev>
Signed-off-by: Robert Detjens <github@detjens.dev>
Signed-off-by: Robert Detjens <github@detjens.dev>
Signed-off-by: Robert Detjens <github@detjens.dev>
Signed-off-by: Robert Detjens <github@detjens.dev>
Signed-off-by: Robert Detjens <github@detjens.dev>
Signed-off-by: Robert Detjens <github@detjens.dev>
Signed-off-by: Robert Detjens <github@detjens.dev>
Signed-off-by: Robert Detjens <github@detjens.dev>
Signed-off-by: Robert Detjens <github@detjens.dev>
detjensrobert
force-pushed
the
dr/frontend-push
branch
from
February 14, 2026 06:41
e0dc239 to
ddbd037
Compare
Signed-off-by: Robert Detjens <github@detjens.dev>
Contributor
|
keeping open until frontend connector to backend is finished |
Signed-off-by: Robert Detjens <github@detjens.dev>
Signed-off-by: Robert Detjens <github@detjens.dev>
Signed-off-by: Robert Detjens <github@detjens.dev>
Signed-off-by: Robert Detjens <github@detjens.dev>
Signed-off-by: Robert Detjens <github@detjens.dev>
Signed-off-by: Robert Detjens <github@detjens.dev>
This struct is only used to validate the structure of the response from Frontend, and is intentionally not used otherwise. Signed-off-by: Robert Detjens <github@detjens.dev>
Co-authored-by: Kai Morita-McVey <kai@moritamcvey.com> Signed-off-by: Robert Detjens <github@detjens.dev>
Co-authored-by: Kai Morita-McVey <kai@moritamcvey.com> Signed-off-by: Robert Detjens <github@detjens.dev>
Signed-off-by: Robert Detjens <github@detjens.dev>
Signed-off-by: Robert Detjens <github@detjens.dev>
Use system CA trust via platform-verifier
KekoaM
requested changes
May 25, 2026
KekoaM
left a comment
Contributor
There was a problem hiding this comment.
Overall looks good to me. Two nits but they do not impact functionality.
| } | ||
| } | ||
|
|
||
| info!(" config ok!"); |
Contributor
Author
Signed-off-by: Robert Detjens <github@detjens.dev>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

@cacama-valvata has provided the schema for what frontend wants for challenge state. This implements that instead of the temporary markdown writeout that we hacked in last year.
This also includes some temporary hacky updates to the challenge
difficultyfield so that it now matches the frontend difficulty config that was moved to be a string instead of an int. This is hacky and the parsing/validation should happen at parse time instead of deploy time but this is enough to make this functional and will be cleaned up as part of #71 anyway.Resolves #62.
Resolves #13.