Actions
Enhancement #25979
closedMigrate custom properties along with node properties for consistency
Status:
Rejected
Priority:
N/A
Assignee:
Category:
Architecture - evolution
Target version:
Effort required:
Name check:
To do
Fix check:
To do
Regression:
No
Description
As see in #25978, not having custom properties at the same place than node properties makes problem.
We used to not be able to do that, because the "ou=Nodes" entry wasn't created before acceptation, which is not the case anymore in 8.X.
This ticket is about migrating everything at the same place, which is rather easy but will need careful testing.
It might go in 8.1, or just in 8.3 because it's really archi evolution.
Updated by François ARMAND about 2 months ago
- Status changed from New to In progress
- Assignee set to François ARMAND
Updated by François ARMAND about 2 months ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Clark ANDRIANASOLO
- Pull Request set to https://github.com/Normation/rudder/pull/6060
Updated by François ARMAND about 2 months ago
- Related to Bug #25978: CustomProperties (inventory properties) are not always correctly retrieved from inventory added
Updated by François ARMAND 20 days ago
- Status changed from Pending technical review to Rejected
OK, so after more thought, I believe we just don't want to do that anymore. Plus, it would be merging fact, ie something that is imposed by the context (for inventory properties), and configuration, ie something that is chosen by the user, and there's no reason to force that now.
Actions