Closed radavis closed 3 months ago
@radavis I still see the feature toggle in the production environment, api.va.gov. Is this expected?
@allanto-ah That's strange because I was able to verify that it was removed in the following support request. I suppose I'll ask to have it removed, again...
https://github.com/department-of-veterans-affairs/va.gov-team/issues/87749
https://github.com/department-of-veterans-affairs/va.gov-team/issues/87912
Half-an-hour after removal, it's showing up in the flipper UI.
We've gone through the steps. The feature toggle is removed from the codebase, which can be verified by searching mhv_landing_page_enabled
and mhvLandingPageEnabled
in vets-website and vets-api. ~As for removing the feature toggle permanently from the production database, this is a higher-level problem that's not going to be solved as part of this ticket.~
Edit: Seems to be a timing issue. Best to wait at least a few days after merging code that removes a feature toggle to run Flipper.remove()
.
@allanto-ah This should be ready for QA, now.
Verified that the feature toggle has been removed from api.va.gov. Also verified that MHV landing page is working as expected
Now that this feature toggle is at 100%, it can be removed.
vets-api
vets-website
Flipper.remove(:mhv_landing_page_enabled)
in development (dev-api.va.gov)Flipper.remove(:mhv_landing_page_enabled)
in staging (staging-api.va.gov)Flipper.remove(:mhv_landing_page_enabled)
in sandbox (sandbox-api.va.gov)Flipper.remove(:mhv_landing_page_enabled)
in production (api.va.gov) [x2]VA Platform docs: Removing old/unused feature toggles