Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • Kea Kea
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 504
    • Issues 504
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 53
    • Merge requests 53
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source Projects
  • KeaKea
  • Issues
  • #334
Closed
Open
Created Dec 10, 2018 by Francis Dupont@fdupontDeveloper

Revamped the require-client-classes idea.

Obviously the require-client-classes feature lacks adoption. My idea is to replace it with a simpler feature which is almost as powerful but more uniform.

Currently we have for host reservations "client-classes" which adds each class of the list to queries matching the reservation. I propose to rename it to "add-client-classes" to avoid confusion with guards and to apply it to scopes where require-client-classes where defined.

The "only-if-required" flag must be changed too: perhaps the original idea of a late evaluation flag should be considered again?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking