-
Notifications
You must be signed in to change notification settings - Fork 1
Disable paging and raise pageSize on NinjaOne array-mode datastreams #52
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
Open
Deenk
wants to merge
1
commit into
main
Choose a base branch
from
work/fw/ninjaone-paging-fixes
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
π΄ This PR modifies 6 data stream files under
plugins/NinjaOne/v1/dataStreams/but does not bump the version inplugins/NinjaOne/v1/metadata.json(still at1.1.9). Per the repo's review guidance, any change inside a plugin directory must include a correspondingmetadata.jsonversion bump; since this is a behavior-affecting paging fix, please add at least a patch bump (e.g.1.1.9->1.1.10) before merging.Extended reasoning...
What the bug is
This PR changes runtime behavior of six NinjaOne data streams (
devices.json,locationDevices.json,locations.json,organizationDevices.json,organizationLocations.json,organizations.json) by switching their paging mode fromtokentononeand adding apageSize: 10000query arg. However,plugins/NinjaOne/v1/metadata.jsonis not modified by the PR and itsversionfield still reads1.1.9.Why this matters
The repo's review instructions are explicit: "Any diff that touches files inside a plugin directory must include a corresponding change to metadata.json that increases the version field. If no version bump is present, assume the task is unfinished and prompt to add one." This is a hard rule, not a stylistic preference β without a version bump, downstream consumers cannot distinguish the fixed plugin from the broken pre-fix one, and the plugin distribution/release pipeline relies on the version field as its sole signal that the contents have changed.
Why existing checks don't catch it
The PR's automated
Plugin PR Summarycheck reportsValidation: β PassedandDeployment: π Deployed, so the CI bot does not enforce the version-bump rule. The breaking-changes checkbox is set to "No", which is consistent with a patch bump (not a major/folder bump), but a patch bump is still required.Impact
Once merged as-is, a user upgrading the plugin would receive the new paging behavior under an unchanged version number β making rollback decisions, support triage, and changelog tracking harder. Any downstream tooling keyed off the version (e.g.
Has been updated since vX.Y.Z) will incorrectly report no change.Step-by-step proof
plugins/NinjaOne/v1/metadata.jsonon this branch βversionis"1.1.9".metadata.json.devices.jsonlines 8-10) β thepagingblock was rewritten frommode: tokenwithpageSize/in/outtomode: none, andgetArgsnow carriespageSize: 10000. This is a clear behavior change.versionto advance to at least1.1.10. It has not.How to fix
Bump
plugins/NinjaOne/v1/metadata.jsonversionfrom1.1.9to1.1.10(patch bump; no breaking change per the PR checkbox) and include it in this PR.