Closed Bug 1333596 Opened 7 years ago Closed 7 years ago

ATMO V2: put LDAP login in an environment variable

Categories

(Cloud Services Graveyard :: Metrics: Pipeline, defect, P3)

Product:
Cloud Services Graveyard
Component:
Metrics: Pipeline
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: spenrose, Unassigned)

References

Details

I'd like to use my login, "spenrose", in scripts. If I share my scripts with someone else, I would like them to use their login. $USER is "hadoop". Can we set a MOZ_USER or something in /home/hadoop/.bashrc?
Points: --- → 1
Priority: -- → P2
Priority: P2 → P3
Could we pick a name for the variable? Then I can have automated jobs test to see if it is set and fall back to my login.
ATMO_USER sounds like a good idea to me, assuming this only applies to ATMO. Or is this something that would also show up in Airflow jobs?
(In reply to Jannis Leidel [:jezdez] from comment #2)
> ATMO_USER sounds like a good idea to me, assuming this only applies to ATMO.
> Or is this something that would also show up in Airflow jobs?

My motivation was to hack emailing into ATMO. Assuming Airflow has notifications, we don't need it there to solve my problem. But might it be generally useful to be able to associate jobs with owners at the environment layer? I have no opinion.
Moved to https://github.com/mozilla/telemetry-analysis-service/issues/214
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
Product: Cloud Services → Cloud Services Graveyard
You need to log in before you can comment on or make changes to this bug.