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.

Sign up for GitHub

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

Jump to bottom

Make sure to perform a deep copy when cloning a resource #8596

Open
FelixGaudin opened this issue Jan 10, 2025 · 0 comments · May be fixed by #8589
Open

Make sure to perform a deep copy when cloning a resource #8596

FelixGaudin opened this issue Jan 10, 2025 · 0 comments · May be fixed by #8589

Comments

@FelixGaudin
Copy link

FelixGaudin commented Jan 10, 2025 •
edited
Loading

When running "read_resource" we usually replace the attributes with values. But if the attribute is a dict and we modify this dict the desired resource also get updated.

It's mostly likely to be cause by the resource.clone()
@FelixGaudin FelixGaudin linked a pull request Jan 10, 2025 that will close this issue
Open
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Improve resource clone inmanta/inmanta-core
1 participant
@FelixGaudin