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

TFRS - Enable Tear-Down Feature Flags for TFRS Dev Environment Testing #1417

Open
AlexZorkin opened this issue Dec 9, 2024 · 0 comments
Open
Assignees
Labels
Medium Medium priority Task Work that does not directly impact the user Tested :) Testing passed

Comments

@AlexZorkin
Copy link
Collaborator

Description:
Activate the front-end feature flags that were introduced during the TFRS teardown work (for both BCeID and IDIR views) within the TFRS Dev environment. These feature flags are currently set to false, allowing all features to remain visible. By turning these flags on (setting them to true), the previously removed or hidden widgets, navigation links, and roles should now disappear, effectively simulating the teardown in the dev environment.

Purpose and Benefit:
Enabling these flags in TFRS Dev will allow the team to test and confirm that the teardown functionality works as intended—removing unnecessary elements from the user interface. This ensures that when it comes time to finalize the teardown in production, the feature flags can be easily flipped to ensure a smooth transition without code changes.

Acceptance Criteria:

  • Given I am a developer, when I set the appropriate environment variables (tear_down.bceid.* and tear_down.idir.*) to true in TFRS Dev, the corresponding widgets, navigation items, and roles are hidden as specified in previous teardown tickets.
  • Given I am a developer, I can verify in TFRS Dev that the removed features do not appear for users under BCeID and IDIR contexts.
  • Given I am a developer, if the flags are reverted to false, the features reappear, confirming the toggle-based nature of this setup.

Development Checklist:

  1. Identify all the existing feature flags related to the teardown for both BCeID and IDIR, for example:

    • tear_down.bceid.widgets.balance
    • tear_down.bceid.widgets.creditTransactions
    • tear_down.bceid.widgets.fileSubmissions
    • tear_down.bceid.header.creditInformation
    • tear_down.bceid.navigation.transactions
    • tear_down.bceid.navigation.fileSubmissions
    • tear_down.bceid.navigation.helpLink
    • tear_down.bceid.organization.creditInformation
    • tear_down.bceid.organization.roles.fileSubmission
    • tear_down.bceid.organization.roles.creditTransfers
    • tear_down.idir.widgets.balance
    • tear_down.idir.widgets.creditTransactions
    • tear_down.idir.widgets.fileSubmissions
    • tear_down.idir.navigation.transactions
    • tear_down.idir.navigation.fileSubmissions
    • tear_down.idir.navigation.helpLink
    • tear_down.idir.organizations.tableColumns.complianceUnits
    • tear_down.idir.organizations.tableColumns.inReserve
    • tear_down.idir.organization.creditInformation
  2. Update the TFRS Dev environment configuration to set these flags to true.

  3. Deploy the changes to TFRS Dev and verify that the UI updates occur as expected:

    • Widgets and navigation items corresponding to these flags should disappear.
    • Credit transfers, file submissions, and other teardown items from previous tickets should no longer be visible.
  4. Document which flags were enabled and their expected effect for future reference.

Testing:

  • Manually inspect TFRS Dev after setting the flags to true to confirm that the features disappear.
  • Potentially create a test user to verify differences in views between BCeID and IDIR contexts.

Notes:
This ticket does not involve writing new code; it only involves updating environment configurations and verifying that the previously implemented teardown logic functions correctly when the flags are toggled.

@AlexZorkin AlexZorkin changed the title LCFS - Enable Tear-Down Feature Flags for TFRS Dev Environment Testing TFRS - Enable Tear-Down Feature Flags for TFRS Dev Environment Testing Dec 9, 2024
@AlexZorkin AlexZorkin added Medium Medium priority Task Work that does not directly impact the user labels Dec 9, 2024
@Grulin Grulin added the Tested :) Testing passed label Jan 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Medium Medium priority Task Work that does not directly impact the user Tested :) Testing passed
Projects
None yet
Development

No branches or pull requests

3 participants