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

ALCS obfuscation 2.0 #1429

Merged
merged 4 commits into from
Feb 15, 2024
Merged

ALCS obfuscation 2.0 #1429

merged 4 commits into from
Feb 15, 2024

Conversation

mhuseinov
Copy link
Collaborator

No description provided.

fake.last_name(),
fake.company(),
fake.phone_number(),
"11@11",
Copy link
Contributor

Choose a reason for hiding this comment

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

It is somewhat common to use that email for testing. Should we leave this as 11@11, or would it be better to have something like obfuscated@email

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I'm using 11@11 as the default email since it will be 100% wrong and will not cause emails to be sent

{get_update_column_query("department")},
{get_update_column_query("phone_number")},
{get_update_column_query("email")},
{get_update_column_query("ocp_bylaw_name")},
Copy link
Contributor

Choose a reason for hiding this comment

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

is ocp necessary to obfuscate? Name of bylaw isn't exactly identifiable info

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

The problem with old data is that sometimes people put info into the wrong field. This field is free input and that is the reason why I'm obfuscating it

{get_update_column_query("email")},
{get_update_column_query("ocp_bylaw_name")},
{get_update_column_query("ocp_designation")},
{get_update_column_query("zoning_bylaw_name")},
Copy link
Contributor

Choose a reason for hiding this comment

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

also here

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

the same as above

Copy link
Collaborator

@trslater trslater left a comment

Choose a reason for hiding this comment

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

LGTM 🚀

@mhuseinov mhuseinov merged commit b1c63d3 into develop Feb 15, 2024
3 checks passed
@mhuseinov mhuseinov deleted the feature/ALCS-1674-obfuscation_2_0 branch February 15, 2024 19:01
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