[$400] Challenge Forum Processor - Archive flow

[jmgasper]

@atelomycterus - With the challenge forum processor, we are going to only have groups "unarchived" when the corresponding challenge is active.

These are the changes we're thinking:

1. When a challenge is initially created (status=New), we'll have the group as archived=true)
2. When a challenge transitions to status=Active, we'll have the group as archived=false)
3. When the challenge completes, is cancelled, or is deleted, we'll have the group as archived=true

This way only active challenges should have an unarchived group

[jmgasper]

Challenge https://www.topcoder.com/challenges/7819a5cf-5ee8-460f-ac45-7d05f44b6829 has been created for this ticket.

This is an automated message for ghostar via Topcoder X

[jmgasper]

Challenge https://www.topcoder.com/challenges/7819a5cf-5ee8-460f-ac45-7d05f44b6829 has been assigned to obog.

This is an automated message for ghostar via Topcoder X

[atelomycterus]

@jmgasper Implemented. More notes about challenge statuses below. Please apply PRs:

• Issues-474: implemented archive flow challenge-forum-processor#55
• Issues-474: synced the categories schema with the categories controller #489
• Issues-474: updated group schema forums-groups-plugin#67

Thanks!

1. When a challenge is initially created (status=New), we'll have the group as archived=true)

I've looked at Topocder challenge-api. It posts events to the 'challenge.notification.create' topic for any status other than Active:
(https://github.com/topcoder-platform/challenge-api/blob/1d77b4869ce4a5745d105ea4a217c0230f6ab1b8/src/services/ChallengeService.js#L836)

I've checked challenge forum processor logs. Most challenges are created with 'Draft' status initially, not 'New' (the 'challenge.notification.create' topic).

In any case, a group is always created as archived = true.

3. When the challenge completes, is cancelled, or is deleted, we'll have the group as archived=true

All cancelled statuses are supported (The list of statuses
https://github.com/topcoder-platform/challenge-api/blob/develop/app-constants.js):

const challengeStatuses = {
  New: 'New',
  Draft: 'Draft',
  Cancelled: 'Cancelled',
  Active: 'Active',
  Completed: 'Completed',
  Deleted: 'Deleted',
  CancelledFailedReview: 'Cancelled - Failed Review',
  CancelledFailedScreening: 'Cancelled - Failed Screening',
  CancelledZeroSubmissions: 'Cancelled - Zero Submissions',
  CancelledWinnerUnresponsive: 'Cancelled - Winner Unresponsive',
  CancelledClientRequest: 'Cancelled - Client Request',
  CancelledRequirementsInfeasible: 'Cancelled - Requirements Infeasible',
  CancelledZeroRegistrations: 'Cancelled - Zero Registrations'
}

[jmgasper]

@sdgun - For testing this one:

1. Create a new challenge in WM. You should be able to open the challenge forum page and see: Archived: true
2. Launch the challenge --> You should be able to open the challenge forum page and see: Archived: false
3. Close the challenge (delete it, cancel it, complete it) --> You should be able to open the challenge forum page and see: Archived: true

I'll walk through this as well, once WM is back up and running properly in dev. Currently it doesn't seem to be working.

[sdgun]

@jmgasper WM is still throwing errors, I will check this in some time.

[jmgasper]

@sdgun / @atelomycterus - In dev, something's broken, but I'm not sure what. Seems like the token we've been using no longer works with adding users to groups, even though the token is for TonyJ, who has Vanilla Admin access. I've logged a new ticket here for investigation: #502

[jmgasper]

@sdgun - This appears to be working, with the fix from #502. Please let me know if you run into any issues - this is the biggest change we're going to push to prod in a couple days.