-
Notifications
You must be signed in to change notification settings - Fork 0
[$50] Change Privacy field on groups #521
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
Comments
Challenge https://www.topcoder.com/challenges/c8338d98-f9d3-4228-9f3c-49c06f20ce42 has been created for this ticket. |
Challenge https://www.topcoder.com/challenges/c8338d98-f9d3-4228-9f3c-49c06f20ce42 has been assigned to obog. |
@jmgasper Need your help with this ticket.
I've checked messages in challenge forum processor logs and challenge API response but Json responses for Challenge processor logschallenge.notification.create:
challenge.notification.update:
Challenge APIM2M token was used, https://api.topcoder-dev.com/v5/challenges/c9904ce5-afd9-4074-958e-9ab000ed34e8:
|
@atelomycterus - Thanks - I'm asking Topcoder if we can add that. |
@atelomycterus - Apparently we have to do this either by specific group IDs or term IDs. I'm still getting more details on what those ID values should be in dev and prod. |
@atelomycterus - Here are the
|
@jmgasper are you ok if the term IDs are hard-coded in Vanilla config are initialized depending on env ?
|
@atelomycterus - Yeah, that's fine. That just means that if we ever want to change it, we'll have to redeploy, correct? I don't anticipate those IDs changing much, if ever. |
@jmgasper Yes, correct. |
@jmgasper Please apply PRS: Thanks! Configs
Testing |
Payment task has been updated: https://www.topcoder.com/challenges/c8338d98-f9d3-4228-9f3c-49c06f20ce42 |
@atelomycterus - One request on the group metadata display was to change the
Privacy
field to be the NDA status of the associated challenge - eitherPublic
orNDA Required
. We should get this flag value with the Kafka message in the challenge forum processor.The text was updated successfully, but these errors were encountered: