Project

General

Profile

Bug #5122

Default location should not scope anything by default

Added by Ivan Necas about 6 years ago. Updated 9 months ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Hosts
Target version:
-
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

Locations are cool feature but they cause more harm than benefit when
the user doesn't explicitly need the feature.

Creating the location with:

  • All users
  • All smart proxies
  • All subnets
  • All compute resources
  • All media
  • All templates
  • All domains
  • All realms
  • All environments
  • All host groups

Should take the locations out of the success path for deployments that don't explicitly need the location stuff.
The user can change that later once they realize they can't live without it

History

#1 Updated by Ivan Necas about 6 years ago

  • Description updated (diff)

#2 Updated by Eric Helms almost 6 years ago

  • Triaged changed from No to Yes

#3 Updated by Eric Helms over 4 years ago

  • Legacy Backlogs Release (now unused) set to 114

#4 Updated by John Mitsch 9 months ago

  • Target version deleted (Katello Backlog)
  • Status changed from New to Rejected

Thanks for reporting this issue. This issue was created over 4 years ago and hasn't seen an update in 1 year. We are closing this in an effort to keep a realistic backlog. Please open up a new issue that includes a link to this issue if you feel this still needs to be addressed. We can then triage the new issue and reassess.

Also available in: Atom PDF