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

[backend] Organization sharing behavior change for upsert and enrichment #6042

Closed
richard-julien opened this issue Feb 19, 2024 · 0 comments · Fixed by #6101
Closed

[backend] Organization sharing behavior change for upsert and enrichment #6042

richard-julien opened this issue Feb 19, 2024 · 0 comments · Fixed by #6101
Assignees
Labels
feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR) upsert & deduplication Linked to system aiming to keep most qualified data
Milestone

Comments

@richard-julien
Copy link
Member

Use case

The platform is currently handling refs differently in term of upsert.
For refs like markings, labels etc its an accumulation to prevent any data loss / data leak
For sharing (granted_refs) is sync/replace each time.
This situation can leads to some inconsistency. So we need to Change the granted_refs behavior to act like marking defs when upserted

Because of changing this behavior we also need to handle the impacts in enrichment process

  • User ask enrichment needs to be done as the connector and not the user
  • Granted_refs needs to be handle correctly by the enrichment connectors to follow this information and so create new enriched data with the correct sharing
  • Playbook operation for remove/replace sharing must be removed as no longer supported.

Data cleaning/fix for this information will need to be done through massive operation in the UI.

This ticket cancel and replace.
#5856
#5857
#5842

@richard-julien richard-julien added the feature use for describing a new feature to develop label Feb 19, 2024
@richard-julien richard-julien self-assigned this Feb 19, 2024
@richard-julien richard-julien added this to the Release 6.0.0 milestone Feb 19, 2024
@richard-julien richard-julien added the solved use to identify issue that has been solved (must be linked to the solving PR) label Feb 27, 2024
@Jipegien Jipegien added the upsert & deduplication Linked to system aiming to keep most qualified data label Jul 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR) upsert & deduplication Linked to system aiming to keep most qualified data
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants