slaveapi should make use of dev staging inventory and mozdns/api/v1_dns

RESOLVED WONTFIX

Status

Release Engineering
Tools
RESOLVED WONTFIX
3 years ago
2 years ago

People

(Reporter: jlund, Assigned: jlund)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

3 years ago
currently we use "https://inventory.mozilla.org/en-US/tasty/v3/" for our inventory api url for both prod and staging.

Furthermore IIUC, this url only allows us certain endpoints like querying machine info (via the '/system' end point) but not for doing things like creating records. 

for creating, invtool itself uses:
A: "https://inventory.mozilla.org:443/en-US/mozdns/api/v1_dns/addressrecord/"
PTR: "https://inventory.mozilla.org:443/en-US/mozdns/api/v1_dns/ptr/"

We should have a uniform url that slaveapi uses, either "mozdns/api/v1_dns" or "/tasty/v3/". I'm assuming it has to be the former

we should also use the dev staging inventory url: "inventory-dev.allimoz.org" on slaveapi-dev1

either way, this will require a dance between a puppet patch (for changing slaveapi.ini) as well as a slaveapi patch for accepting the new api_url.
(Assignee)

Updated

3 years ago
Summary: slaveapi should make use of dev staging inventory. → slaveapi should make use of dev staging inventory and mozdns/api/v1_dns/ptr
(Assignee)

Updated

3 years ago
Summary: slaveapi should make use of dev staging inventory and mozdns/api/v1_dns/ptr → slaveapi should make use of dev staging inventory and mozdns/api/v1_dns
(Assignee)

Comment 1

2 years ago
In Bug 1019732, I ended up going with an in-line replace urls when doing a POST request as I don't see any inventory work being done for this in the near term
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.