Closed Bug 1518292 Opened 5 years ago Closed 5 years ago

Environment in JEXL context should be `env`, not `environment`

Categories

(Firefox :: Normandy Client, defect)

60 Branch
defect
Not set
normal

Tracking

()

RESOLVED FIXED
Firefox 66
Tracking Status
firefox66 --- fixed

People

(Reporter: glasserc, Assigned: glasserc)

References

Details

Attachments

(1 file)

In bug 1477255, I filed a patch creating an alias called environment, but per discussion on the bug, it should instead be called env.

Fortunately, I don't think any recipes use this yet so it should be easy to fix.

Blocks: 1477255

leplatrem: The original bug had a stated goal of Normandy and Remote Settings being compatible with what the context was named. I don't think any Normandy recipes use environment yet so we can switch it to env very easily. What about Remote Settings? I see there's already support for environment -- do you know if any settings use that? If so, I guess we need to maintain that for backwards compatibility, at least on the Remote Settings side.

Flags: needinfo?(mathieu)

We don't have any settings entries that have JEXL experessions, and AFAIK none of our current use-cases are designed to leverage them.

I would say that we're safe to rename it to env.

Flags: needinfo?(mathieu)
Keywords: checkin-needed
Assignee: nobody → eglassercamp

Pushed by apavel@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/b0858dddedf9
use env instead of environment in JEXL context r=Gijs

Keywords: checkin-needed
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 66
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: