[$300] M2M handling and v4/v3 API

[jmgasper]

@afrisalyp - There are bugs in the v4 API in prod that don't seem like they are going to be fixed anytime soon, unfortunately, and that don't show up in dev.

What we are going to do is:

1. Remove the M2M token generation, moving back to the service account we used to use, before the change here: Update to use M2M token for Topcoder-X #128
2. Change from using the v4 API back to v3. This will cause other problems, but at least it's the same problems we used to have, and not new problems.

[jmgasper]

Contest https://www.topcoder.com/challenges/30108027 has been created for this ticket.

This is an automated message for ghostar via Topcoder X

[jmgasper]

Contest https://www.topcoder.com/challenges/30108028 has been created for this ticket.

This is an automated message for ghostar via Topcoder X

[jmgasper]

Contest https://www.topcoder.com/challenges/30108029 has been created for this ticket.

This is an automated message for ghostar via Topcoder X

[jmgasper]

Contest https://www.topcoder.com/challenges/30108030 has been created for this ticket.

This is an automated message for ghostar via Topcoder X

[jmgasper]

[500]: Can't find the issue in DB. It's not found or not accessible

This is an automated message for ghostar via Topcoder X

[jmgasper]

[500]: Can't find the issue in DB. It's not found or not accessible

This is an automated message for ghostar via Topcoder X

[jmgasper]

Contest https://www.topcoder.com/challenges/30108031 has been created for this ticket.

This is an automated message for ghostar via Topcoder X

[jmgasper]

Contest https://www.topcoder.com/challenges/30108032 has been created for this ticket.

This is an automated message for ghostar via Topcoder X

[jmgasper]

[500]: Can't find the issue in DB. It's not found or not accessible

This is an automated message for ghostar via Topcoder X

[jmgasper]

[500]: Can't find the issue in DB. It's not found or not accessible

This is an automated message for ghostar via Topcoder X

[afrisalyp]

@jmgasper

Remove the M2M token generation, moving back to the service account we used to use, before the change here: #128

Do we need to completely remove the M2M token mechanism? Or we just can leave it unused or commented?

[jmgasper]

@afrisalyp - We can just comment it out for now.

[afrisalyp]

@jmgasper - It seems that the dev doesn't work with the v3 API.
I think it's a good idea to keep the dev with the v4 API. So we change only the prod to v3 API.
Is that acceptable?

[jmgasper]

@afrisalyp - Yes, that's fine, thanks.

[jmgasper]

Contest https://www.topcoder.com/challenges/30108039 has been created for this ticket.

This is an automated message for ghostar via Topcoder X

[jmgasper]

Contest https://www.topcoder.com/challenges/30108040 has been created for this ticket.

This is an automated message for ghostar via Topcoder X

[jmgasper]

Contest https://www.topcoder.com/challenges/30108041 has been created for this ticket.

This is an automated message for ghostar via Topcoder X

[jmgasper]

Contest https://www.topcoder.com/challenges/30108042 has been created for this ticket.

This is an automated message for ghostar via Topcoder X

[jmgasper]

[500]: Challenge for the updated issue 251 is creating, rescheduling this event

This is an automated message for ghostar via Topcoder X

[jmgasper]

Contest https://www.topcoder.com/challenges/30108043 has been created for this ticket.

This is an automated message for ghostar via Topcoder X

[jmgasper]

Contest https://www.topcoder.com/challenges/30108190 has been created for this ticket.

This is an automated message for ghostar via Topcoder X

[jmgasper]

Contest https://www.topcoder.com/challenges/30108190 has been updated - it has been assigned to afrisalyp.

This is an automated message for ghostar via Topcoder X

[jmgasper]

Payment task has been updated: https://software.topcoder-dev.com/review/actions/ViewProjectDetails?pid=30108190

This is an automated message for ghostar via Topcoder X