Closed Bug 1515138 Opened 6 years ago Closed 4 years ago

Stub installer ping pipeline support for AArch64

Categories

(Data Platform and Tools Graveyard :: Operations, enhancement)

Product:
Data Platform and Tools Graveyard
Component:
Operations
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: molly, Unassigned)

References

Details

(Whiteboard: [DataOps])

Currently the stub installer (DSMO) ping has boolean fields "64bit_os" and "64bit_build" that indicate the architecture of the Windows installation and of the copy of Firefox being installed. We're adding a third platform, AArch64, in addition to x86 and x86_64, so booleans no longer do the job. There's a couple different ways we handle do this in the ping URL; right now the booleans are sent there as 0 or 1, so I can easily add a 2 for the new case. Or I can turn them into strings. Doesn't matter to me, both of those are easy from the client end. But I'm not sure what the backend/pipeline implications of this change are or what might be done to smooth that out.
Flags: needinfo?(bimsland)
Component: Redash (STMO) → Operations
Flags: needinfo?(bimsland)
QA Contact: moconnor
Whiteboard: [DataOps]

I'm implementing the parsing for this for GCP ingestion, and it would be easier for me to handle a 2 for the new case.

From what I can tell we didn't actually decide anything here and the GCP ingestion code treats this as a boolean, as do schemas.

AFAICT from downstream bugs this isn't needed; reopen if it is.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
Product: Data Platform and Tools → Data Platform and Tools Graveyard
You need to log in before you can comment on or make changes to this bug.