Project

General

Profile

Bug #19728

Set User.current in rake console

Added by Lukas Zapletal almost 6 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Category:
Rake tasks
Target version:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

With security patch that want into 1.14 and develop many models are more restricted now and console is mostly unusable without user set. Let's explicitly set the user to anonymous admin and tell the user to change this if needed.

Associated revisions

Revision 987aa983 (diff)
Added by Lukas Zapletal almost 6 years ago

Fixes #19728 - set admin user in rake console

Revision 0d70706b (diff)
Added by Lukas Zapletal almost 6 years ago

Fixes #19728 - set admin user in rake console

History

#1 Updated by The Foreman Bot almost 6 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Lukas Zapletal
  • Pull request https://github.com/theforeman/foreman/pull/4563 added

#2 Updated by Ohad Levy almost 6 years ago

TBH I prefer not to, I think that if you are using the console, you should be aware, otherwise it might lead to unexpected pain?

#3 Updated by Lukas Zapletal almost 6 years ago

  • Legacy Backlogs Release (now unused) set to 248

After discussion on IRC, we agreed this is a regression and it needs to be fixed. We will create an extra console_admin for recording purposes.

#4 Updated by Daniel Lobato Garcia almost 6 years ago

  • Legacy Backlogs Release (now unused) deleted (248)

I don't think this is 1.15.1 worthy. It adds a feature - console isn't part of "Foreman" and it isn't fixing any bug as far as I understand.

#5 Updated by The Foreman Bot almost 6 years ago

  • Pull request https://github.com/theforeman/foreman/pull/4565 added

#6 Updated by Lukas Zapletal almost 6 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#7 Updated by Marek Hulán almost 6 years ago

  • Legacy Backlogs Release (now unused) set to 248

Also available in: Atom PDF