fix(pebble)!: change select=all to users=all for pebble get_notices #1146
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Pebble added support for notices, aggregated events that are recorded with a type and key. The
/v1/notices
API had a parameter "select=all" to show notices for all users, and the parameter name is changed to "users=all" in recent release v1.9.0.This PR is the corresponding changes to the ops framework.
Related doc: OP042 - User ID features for Pebble Notices
Issue
See here: #1132
Changes
pebble.Client.get_notices
model.Container.get_notices
Unit Test
For pebble:
Some Manual Test
Start pebble:
Run some CLI commands like
pebble notify example.com/hello
.Import local code and test: