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

DG-1735 | Retry policy download for Atlas service if latest change is not found #3393

Merged
merged 11 commits into from
Aug 13, 2024

Conversation

krsoninikhil
Copy link

@krsoninikhil krsoninikhil commented Aug 13, 2024

Change description

There were few cases reported where changes shown in audit logs for the policies created on a new connection creation where not reflecting while policies were fetched. This adds retries attempt with some delay to incorporate possible delay in ES sync with Cassandra.

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

bichitra95 and others added 11 commits August 1, 2024 14:53
DQ-343 Datatype change for owners attr in Contracts
Instead of proceeding with refreshing the atlas_tag policies,
this is will throw the exception so the last sync time is not
updated and next run again sees the audit logs
Previously used timestamp would never detect the delete event
as the entity update time doesn't get updated on delete
Without this check, policy download API check could take the
Persona or Purpose update time to be last edit time
for which it will not find a policy since no policy
exist for this mistakenly considered timestamp.
@krsoninikhil krsoninikhil merged commit e3f5a0a into staging Aug 13, 2024
14 of 15 checks passed
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