Comment on Privacy disaster as LGBTQ+ and BDSM dating apps leak private photos.

• sugar_in_your_tea@sh.itjust.works ⁨1⁩ ⁨month⁩ ago

  Why would you have regression on prod? Or why would you care what the password is on staging environments?

  We have our lower environments (where all testing happens) on a VPN completely separated from prod, and testing engineers only ever touch those lower environments. Our Ops team manages all admin prod accounts, and those are completely separate from lower environment accounts.

  So I guess I’m struggling to understand the issue here. Surely you could keep a crappy password for pre-prod testing? We even create a copy of prod as needed and change the admin accounts if there’s something prod-specific.

  source

  • yoshman@lemmy.world ⁨1⁩ ⁨month⁩ ago

    The production database gets down-synced to the lower environments on demand, so they can test on actual production datasets. That would require us to manually remake this user account every time a dev down-syncs the database to a lower environment.

    The customer is paranoid, as the project is their public facing website, so they want testing against the actual prod environment.

    We don’t mange the SSO, as that is controlled by the customer. The only local (application specific) account is this account for testing.

    source

    • sugar_in_your_tea@sh.itjust.works ⁨1⁩ ⁨month⁩ ago

      That would require us to manually remake this user account

      That sounds fine? Just add it to the script when down-syncing. Or keep auth details in a separate DB and only sync that as needed (that’s what we do).

      The customer is paranoid, as the project is their public facing website, so they want testing against the actual prod environment.

      That’s the main problem then, not this testing engineer. We do test directly on prod, but it’s not our QA engineers doing the testing, but our support staff and product owners (i.e. people who already have prod access). They verify that the new functionality works as expected and do a quick smoke test to make sure critical flows aren’t totally busted. This covers the “paranoid customer” issue while also keeping engineers away from prod.

      Maybe you’re doing something like that now, idk, but I highly recommend that flow.

      source

      • yoshman@lemmy.world ⁨1⁩ ⁨month⁩ ago

        We resolved it by making him use pipeline vars for his scripts. Like we told him to do in the beginning.

        He fought it because he wanted his scripts the same for all projects. Including hard coded usernames and passwords. So, it was mostly his fault.

        source

        • -> View More Comments