Skip to content

Conversation

surajkn
Copy link
Collaborator

@surajkn surajkn commented Sep 18, 2023

This will allow us to control which datastream update checks to override

Important: DO NOT REPORT SECURITY ISSUES DIRECTLY ON GITHUB.
For reporting security issues and contributing security fixes,
please, email [email protected] instead, as described in
the contribution guidelines.

Please, take a minute to review the contribution guidelines at:
https://github.com/linkedin/Brooklin/blob/master/CONTRIBUTING.md

This will allow us to control which datastream update checks to override
@surajkn surajkn requested a review from thomaslaw September 18, 2023 20:02
+ " old: %s new: %s", key, oldDatastream, datastream));
}

if (!_config.getOverrideDatastreamUpdateChecks()) {
Copy link
Collaborator

Choose a reason for hiding this comment

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

So this flag only allows you to bypass the destination check? Why is this needed and if it is should we rename it?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yes for now we only bypass destination change check. For IPv6, we plan to manually (through brooklin tool command) update destination of the exisiting datastreams, and this check prevents that.
This is only a temporary change. Once IPv6 migration is done we will revert this change. So not a lot of benefit in renaming it if you dont feel too strongly about it

Copy link
Collaborator

Choose a reason for hiding this comment

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

If the plan is to revert that's fine

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.

3 participants