Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Attack/Defence: Teams #52

Open
libkush opened this issue Feb 1, 2025 · 1 comment · May be fixed by #69
Open

Attack/Defence: Teams #52

libkush opened this issue Feb 1, 2025 · 1 comment · May be fixed by #69
Assignees
Labels
easy Good for newcomers high priority

Comments

@libkush
Copy link

libkush commented Feb 1, 2025

Team (Attack/Def)

Create an implementation of a team entity for round 2 (attack/defence style CTFs) and it's corresponding CRUD endpoints in the API.

Models Required1

  • AttackDefTeam:
    • team: Foreign key of Team model. Represents the team participating in the attack/def style competition.
    • powerups: String Enumerator. Represents the powerup(s) currently activated by the team which will be removed once the effect is achieved and/or time limit reached.
    • ctfs: Reverse relation on AttackDefProblem model. Represents all the CTFs belonging to this team that the other teams can attack and gain points.

API Endpoints2

  • Modify existing team signup endpoint to also initialize columns team_attackdef. (This model will be created for each team during Round 2 CTF allocation.)

  • GET /ctfs

    • List all the CTFs belonging to the team.
  • GET /powerups

    • Lists all the powerups currently activated by the team.

Footnotes

  1. Models subject to change as per requirements.

  2. API endpoints subject to change as per requirements.

@libkush libkush changed the title Attack/def: Teams Attack/Defence: Teams Feb 2, 2025
@ThEditor ThEditor added high priority easy Good for newcomers labels Feb 7, 2025
@tnmkr
Copy link

tnmkr commented Feb 8, 2025

I'm working on this issue.

@tnmkr tnmkr linked a pull request Feb 17, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
easy Good for newcomers high priority
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants