Skip to content

Improve support for centrally managed mementos #3398

@eddybl

Description

@eddybl

The Issue

Currently, memenots exist in the user space at one location. There is no simple way to provide centrally managed mementos in addition to user-controlled/personal mementos.

Workarounds

There are some options to work around this issue. For example #2435 discusses the option of copying central mementos into the user space directory.

But the problem is that a simple file copy is not the same as a managed file. For example over time, if centrally managed memenots evolve (change name or get removed) they still exist in the user space.

Possible Solution

I think a cleaner option would be to add second (optional) memento look-up location, which can be configured via the settings. With this, there would be no need to mess with the user space mementos. This second location could then be:

  • just an additonal manually managed folder somewhere else
  • a folder fully managed by salt/ansible
  • a folder fully managed by launcher scripts
  • a remote location?

Implications for the GUI

Phoebus then would need to process both locations and in some form "merge" the mementos for the user to select from. The following options come to mind for the navigation menu;

  1. do nothing extra, just present memenots from both locations in the same list
  2. add a horizontal line seperator to distingiush the two locations
  3. add another navigation level (right arrow which opens another menu) either just for the second location or both

To keep the impact low for people who do not want to use that, this feature could be behind a feature flag (probably not relevant for option 1)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions