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

POLICY-166: Linking and Unlinking API improvements #3912

Draft
wants to merge 29 commits into
base: master
Choose a base branch
from

Conversation

arpit-at
Copy link

Change description

Description here
Changes linking and unlinking policy API to support Rules in business policy
https://atlanhq.atlassian.net/wiki/spaces/Governance/pages/545882180/Linking+API+Documentation

Type of change

  • Bug fix (fixes an issue)
  • New feature (adds functionality)

Related issues

Fix #1

Checklists

Development

  • Lint rules pass locally
  • Application changes have been tested thoroughly
  • Automated tests covering modified code pass

Security

  • Security impact of change has been considered
  • Code follows company security practices and guidelines

Code review

  • Pull request has a descriptive title and context useful to a reviewer. Screenshots or screencasts are attached as necessary
  • "Ready for review" label attached and reviewers assigned
  • Changes have been reviewed by at least one other contributor
  • Pull request linked to task tracker where applicable

@arpit-at arpit-at changed the title Arpitbulklinkingmaster POLICY-166: Linking and Unlinking API improvements Dec 24, 2024
.github/workflows/maven.yml Outdated Show resolved Hide resolved
import org.apache.commons.lang3.StringUtils;
import org.javatuples.Pair;

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

imports are not used, please remove

Set<String> newCompliantPolicies = data.getComplaintPolicies();

// Calculate effective compliant and non-compliant policies
Set<String> effectiveCompliant = calculateEffectivePolicies(existingCompliant, newCompliantRules, newCompliantPolicies);

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

instead of existingCompliant/newCompliantRules/newCompliantPolicies, can we rewrite as existingCompliantGuids/newCompliantRuleGuids/newCompliantGuids

Overall, suggesting mentioning that all these fields stores policy/Rule GUIDs
This also applies to the fields in the model class BusinessPolicyRequest.AssetData

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have changed it, but not in AssetData, as it will require making the changes in all the integrations everywhere but I have added clarifying comments on top of each attribute, hope it works

@arpit-at arpit-at requested a review from nikhilbonte21 January 2, 2025 12:59
nikhilbonte21
nikhilbonte21 previously approved these changes Jan 6, 2025
@arpit-at arpit-at marked this pull request as draft January 6, 2025 05:27
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

Successfully merging this pull request may close these issues.

2 participants