1035139 - Make One and Done REST API key publicly available to users

Status: RESOLVED WONTFIX

(Mozilla QA Graveyard :: One and Done, defect, P4)

Description

[Pankaj Malhotra (:bitgeeky)]

This bug is to make the One and Done API key publicly available to volunteers who want to run the tests also add an entry to webqa-credentials repository.

Comment 1

[Pankaj Malhotra (:bitgeeky)]

Bob, there is already a user with email id [e-mail] on the oneanddone staging website.
Also there is an entry of API key in webqa-credentials repository for the same user.

Please let me know, if I just now need to add the same API key as a default value in credentials.yaml for oneanddone-tests repository or also need to do something else ?

Comment 2

[Bob Silverberg [:bsilverberg]]

bitgeeky: We should discuss this at this week's Web QA meeting to see if anyone has any questions or concerns about this. I'm unsure about a few things, including:

1. I don't think we should add it to the default credentials.yaml file as then we have no knowledge or control over who has it. I think we should manually hand it out to contributors as needed.

2. I'm not sure if we should use the one already in webqa-credentials to hand out to contributors, or whether we should perhaps create a new one just for that purpose.

Comment 3

[Pankaj Malhotra (:bitgeeky)]

In the Web QA meeting we discussed to add the API key to the credentials file.
So Bob should I use the same user(the one with email id [e-mail]) or create a new one ?

Comment 4

[Bob Silverberg [:bsilverberg]]

I have an action item to follow up with the Socorro devs about how they handle this. I will do that this afternoon and update this bug.

Comment 5

[Bob Silverberg [:bsilverberg]]

Socorro has a whole interface within the tool that allows users to create their own API keys. While this is pretty cool, I don't see us taking the time to implement something like that.

I believe that once the dependent bugs are resolved for this bug we will be in a position to hand out API keys to users, but that the process will remain manual for now.

Comment 6

[Bob Silverberg [:bsilverberg]]

We are no longer using the REST API to populate test data, so this is no longer needed.