-
Notifications
You must be signed in to change notification settings - Fork 22
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
Dirty-tracking for not-changes attributes? #31
Comments
This would be a great feature, since I am syncing data from a management tool to netbox. |
I'm happy to review and merge if you find time for a PR. |
I added the code which I thought would be best to implement this feature, however it breaks the test suite and I don't know why exactly. Maybe some of the tests are actually using the fact that dirty_data is being set when the object is actually not changed?
In the
Do you have any suggestions? |
I don't really have time to look into it too deeply ATM. But if you make an MR, I can have a look at the failing specs. |
Hi thde, |
I'm currently importing a larger number of configurations from different sources into Netbox, and this causes a lot of (unnecessary) PATCH requests.
Let's say I've got this device role, created by a previous import run:
When setting its attributes, it gets tracked:
Should
NetboxClientRuby::Entity#method_missing
track dirty attributes when the value did not change?The patch should be relatively easy:
The text was updated successfully, but these errors were encountered: