Actions
Feature #15741
closedUse parameter_filter instead of attr_accessible
Description
Foreman is dropping support for protected_attributes and we need to switch to their new way of whitelisting attributes. See here for more info:
Here's the Foreman PR:
Updated by David Davis over 8 years ago
- Related to Bug #3659: "no implicit conversion of URI::HTTP into String" running rake reports:summarize added
Updated by David Davis over 8 years ago
- Related to deleted (Bug #3659: "no implicit conversion of URI::HTTP into String" running rake reports:summarize)
Updated by David Davis over 8 years ago
- Related to Feature #3917: Add strong_parameters to foreman added
Updated by David Davis over 8 years ago
One option would be to add protected_attributes as a dependency for Katello but I'd probably recommend against it. We use strong_params pretty much everywhere--except when extending the foreman models. We call attr_accessible in about 8 places that I think we can switch over to parameter_filter. I am going to investigate that route.
Updated by The Foreman Bot over 8 years ago
- Status changed from New to Ready For Testing
- Assignee set to David Davis
- Pull request https://github.com/Katello/katello/pull/6194 added
Updated by David Davis over 8 years ago
- Has duplicate Bug #5158: Remove attr_accessible from Katello added
Updated by Justin Sherrill over 8 years ago
- Translation missing: en.field_release set to 162
- Difficulty set to hard
Updated by Anonymous over 8 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset katello|328ee19afa9b743d6ff25e3c7cabaa20c87b43cc.
Updated by David Davis over 8 years ago
- Has duplicate Bug #16109: db_seed fails with Host::Managed is using attr_accessible so must either be converted to strong parameters, or add the protected_attributes gem added
Actions