Skip to content

Drop password columns#2335

Merged
jmhooper merged 1 commit intomasterfrom
jmhooper-drop-password-columns
Jul 24, 2018
Merged

Drop password columns#2335
jmhooper merged 1 commit intomasterfrom
jmhooper-drop-password-columns

Conversation

@jmhooper
Copy link
Contributor

Why: The app is no longer reading from these columns

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**: The app is no longer reading from these columns
@jmhooper jmhooper force-pushed the jmhooper-drop-password-columns branch from 0fa1323 to 0309d8f Compare July 18, 2018 15:50
@jmhooper
Copy link
Contributor Author

I am going to wait until prod is deployed before merging this.

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. Let's wait until we deploy RC 62 before merging this.

@monfresh
Copy link
Contributor

Ha. jinx

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.

3 participants