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

migration is calling for it to fetch every policy #102

Open
sbryant82 opened this issue Feb 28, 2024 · 2 comments
Open

migration is calling for it to fetch every policy #102

sbryant82 opened this issue Feb 28, 2024 · 2 comments

Comments

@sbryant82
Copy link

Using 7.4.2
Selective migration>policies
when migrating a single policy, looking at the logs the app is fetching every policy in the database before it starts migrating. This is taking a long time with a current total of 184 policies in our database.

@sbryant82
Copy link
Author

image

@BIG-RAT
Copy link
Contributor

BIG-RAT commented Feb 28, 2024

Using migrate dependencies I trust. That can cause package lookups, and yes every package. The reason for that is the API allows you to create multiple package records in Jamf Pro (with different display names) that point to the same package file name. For example you could potentially have a listings in Jamf Pro for, say, OneDrive.pkg with a display name of OneDrive.pkg and another listing to that same package with a display name of OneDrive (no extension). Only one of those listings is valid.
Like to find a better way to guard against this but haven't come up with anything yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants