#7516 the-new-hotness - Add bugzilla API key to secrets
Closed: Fixed 8 months ago by kevin. Opened 8 months ago by zlopez.

  • Describe what you need us to do:
    I need from you to generate API key for the current user used by the-new-hotness upstream_release_bugzilla_user.
    To do this log with the user and go to Preferences -> API Keys.

  • When do you need this? (YYYY/MM/DD)
    As soon as possible

  • When is this no longer needed or useful? (YYYY/MM/DD)
    When bugzilla will not end session abruptly for logged user

  • If we cannot complete your request, what is the impact?
    the-new-hotness will not be able to fill bugs in bugzilla


Done. This api token is now in the 'upstream_release_bugzilla_api_token' variable.

:paperclip:

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

8 months ago

Just a question: Will this API token work for both staging and production?

@zlopez hopefully the staging instance is not configured to use the production bugzilla. It probably should be configured to use the partner bugzilla.

An API token on production bugzilla would not work on partner bugzilla.

@bowlofeggs Yes, the staging is using partner bugzilla.

I was just curious about this, because according to the current hotness configuration the user is the same for both staging and production.

But it looks like I need two API keys for staging and production.

It's my bad I didn't said this clearly.

Login to comment on this ticket.

Metadata