Project

General

Profile

Actions

Bug #23763

closed

notifications and blueprints API for CRUD

Added by Thomas McKay almost 6 years ago. Updated almost 3 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Notifications
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

There is no notifications api for creating notices or blueprints. Exposing this would be valuable for external tools and scripts that interact with foreman.

Some examples from katello space:
+ an external tool uses forces a new repository sync and wishes to make that known to users
+ a content view promotion is ready for approval through foreman-hooks

An api would also allow a notifications ui page where notices may be seen in more detail. Right now they are ephemeral with no history.

Actions #1

Updated by Marek Hulán almost 6 years ago

  • Status changed from New to Need more information

I might be missing something, but blueprint is something, that differs per notification type and must defined and seeded by the plugin. What kind of DSL would you expect? See e.g. this PR for example how to add new notifications - https://github.com/theforeman/foreman_remote_execution/pull/301/files

Actions #2

Updated by Thomas McKay almost 6 years ago

  • Status changed from Need more information to New

I am not very familiar with the code but as a user I'd want to create custom notifications. Should I have access to an api to create custom blueprints or should there be a single static blueprint that can be used by api?

Actions #3

Updated by yifat makias almost 3 years ago

  • Status changed from New to Rejected

Sorry but we do not see this implemented in the future

Actions

Also available in: Atom PDF