Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(Backport 5.2) - Use Stream Names for Content Packs #17609

Conversation

ryan-carroll-graylog
Copy link
Contributor

Backport of #17089 to 5.2.

* Use stream names for content packs

* Cleanup

* Fix install

* cleanup

* remove unused import

* Handle multiple streams better, minor name refactoring

* Add handling for the rest of the entity types that reference streams

* Fix line spacing

* Add missing license header

* Fix failing tests

* Add changelog entry

* Return StreamReference Entity Exerpts to front end to ensure proper handling of existing entities

* Use Stream title to generate excerpt IDs to avoid collision with regular Streams. Irrellevant to content packs but was causing problems for start page and related tests.

* Add default naive implementation of StreamService loadAllByTitle()

* Resolve stream deps for dashboard widgets
@ryan-carroll-graylog ryan-carroll-graylog changed the base branch from master to 5.2 December 6, 2023 19:40
@ryan-carroll-graylog ryan-carroll-graylog marked this pull request as ready for review December 7, 2023 13:09
Copy link
Contributor

@danotorrey danotorrey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good and tests successfully on 5.2!

@ryan-carroll-graylog ryan-carroll-graylog merged commit 64c8be5 into 5.2 Dec 8, 2023
5 checks passed
@ryan-carroll-graylog ryan-carroll-graylog deleted the backport-5.2/16885-update-content-pack-system-to-handle-streams-by-name-rather-than-id branch December 8, 2023 19:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants