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

LG-163 Turn on agency based UUIDs #2076

Merged
merged 1 commit into from
Apr 11, 2018

Conversation

stevegsa
Copy link
Contributor

@stevegsa stevegsa commented Apr 2, 2018

Why: We need to share agency-specific UUIDs as well as facilitate sharing of an agency’s UUID with other agencies. We also need a way to count the unique number of users for an agency for billing purposes

How Change the feature flags associated with agency based uuids. Specifically we are changing the environment variables enable_agency_based_uuids and agencies_with_agency_based_uuids to include all agencies.

Hi! Before submitting your PR for review, and/or before merging it, please
go through the following checklist:

  • For DB changes, check for missing indexes, check to see if the changes
    affect other apps (such as the dashboard), make sure the DB columns in the
    various environments are properly populated, coordinate with devops, plan
    migrations in separate steps.

  • For route changes, make sure GET requests don't change state or result in
    destructive behavior. GET requests should only result in information being
    read, not written.

  • For encryption changes, make sure it is compatible with data that was
    encrypted with the old code.

  • For secrets changes, make sure to update the S3 secrets bucket with the
    new configs in all environments.

  • Do not disable Rubocop or Reek offenses unless you are absolutely sure
    they are false positives. If you're not sure how to fix the offense, please
    ask a teammate.

  • When reading data, write tests for nil values, empty strings,
    and invalid formats.

  • When calling redirect_to in a controller, use _url, not _path.

  • When adding user data to the session, use the user_session helper
    instead of the session helper so the data does not persist beyond the user's
    session.

  • When adding a new controller that requires the user to be fully
    authenticated, make sure to add before_action :confirm_two_factor_authenticated.

**Why**: We need to share agency-specific UUIDs as well as facilitate sharing of an agency’s UUID with other agencies. We also need a way to count the unique number of users for an agency for billing purposes

**How** Change the feature flags associated with agency based uuids.  Specifically we are changing the environment variables enable_agency_based_uuids and agencies_with_agency_based_uuids.
@stevegsa stevegsa changed the title LG-79 Turn on agency based UUIDs LG-163 Turn on agency based UUIDs Apr 2, 2018
Copy link
Contributor

@monfresh monfresh left a comment

Choose a reason for hiding this comment

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

LGTM

@monfresh
Copy link
Contributor

When do we want this to take effect?

@stevegsa
Copy link
Contributor Author

The plan was to send it out with the normal prod deploy for the current sprint and run some rake tasks in prod beforehand.

@stevegsa stevegsa merged commit 86f288e into master Apr 11, 2018
@amathews-fs amathews-fs deleted the stevegsa-turn-on-agency-based-uuids branch January 7, 2021 18:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants