Skip to content

New projects do not respect cascading settings value for duo_features_enabled

Problem

For duo_features_enabled, the setting cascades from application settings to groups to subgroups to projects.

Whenever the setting value is changed at a higher level, the setting value is updated for all children via a sidekiq job.

When a new group is created, the default value of duo_features_enabled is nil. In order to determine what value to use, the group looks at the value of the setting at parent group level. If that is also nil, it looks for the value at the application level.

When a new project is created, however, the default value of duo_features_enabled is always true.

Instead, when a new project is created it should inherit the duo_features_enabled value of its parent group.