#10547 [release-monitoring] Bugzilla API Key for the-new-hotness on staging
Closed: Fixed 2 years ago by kevin. Opened 2 years ago by zlopez.

Describe what you would like us to do:


Currently the-new-hotness is using username and password for authentication on staging. Because of the upcoming Bugzilla changes it would be best to generate API token for the user that is currently logging in. See hotness ansible configuration for the exact variable.

I already removed the option to log in using username and password from hotness, so with next release the API key will be the only option.

Please generate bugzilla API token for hotness in staging and add it to secrets.

When do you need this to be done by? (YYYY/MM/DD)


2022/02/28


Metadata Update from @mohanboddu:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: medium-gain, medium-trouble, ops

2 years ago

ok, I generated a token and it's in ansible-private, stored as: upstream_release_bugzilla_api_token_stg

Let me know if you run into any issues with it.

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

2 years ago

Login to comment on this ticket.

Metadata
Boards 1
ops Status: Backlog