Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • feudalClient feudalClient
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • feudal
  • feudalClientfeudalClient
  • Issues
  • #17

Closed
Open
Created Jul 01, 2020 by uros.stevanovic@yt8006Developer

Updated information about the user is not propagated to services

User can change some values via GUI (e.g. SSH key, and username). That information is typically then propagated to the services where user is deployed. However, when the information is updated via REST API, that is not so, except for SSH keys. User can have a new entitlement (which indicates which services he should be deployed or undeployed to), or similar. Expected behavior is that FEUDAL reacts to the new information, and send it to services where user is deployed.

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

Imprint