normandy
normandy copied to clipboard
Firefox recipe server
We've talked about setting up email notifications for things like recipes that need approval, etc. Relud had an interesting request this morning. Email notifications only for recipes that get published....
It looks like when we check certificates, we need to be a bit more careful about the exceptions that can be thrown by the network. https://sentry.prod.mozaws.net/operations/normandy-stage/issues/614319/ ``` ...snip File "normandy/health/api/views.py",...
#599, #584 and #586 all involve adding server-side behavior that is custom to a specific type of action, and there's potentially confusing edge cases for recipes that change their action....
The [`show-heartbeat` documentation](http://normandy.readthedocs.io/en/latest/user/actions/show-heartbeat.html) is out-of-date with recent additions (such as the 24-hour delay between showing individual Heartbeat prompts. We should update it. @andymikulski You're most familiar with the new options...
Currently, we only expose recipe arguments and filter objects as a raw JSON string in graphql. For example, the query `{recipe(id:755){latestRevision{argumentsJson filterObjectsJson}}}` results in this response: ```json { "data": {...
We are not currently documenting a number of JEXL transforms: - `length` - `mapToProperty` - `regExpMatch` - `versionCompare`
In #1844 we restricted the fields on `UserType` but we should do this for all types.
The new contract tests work in CI (sometimes, see #1826), but don't pass against prod and stage. Looking at the problems in the test failures, it is definitely a shortcoming...
see: https://sentry.prod.mozaws.net/operations/normandy-prod/issues/5401918/?query=is:unresolved The error is: KeyError 'Unable to update a record, need an id.' I tried it twice and it failed. Rehan tried it a minute or so later and...
Ecosystem QA needs documentation about all the current v1 API calls to determine if additional contract tests are needed.