Uploaded image for project: 'Stripes'
  1. Stripes
  2. STRIPES-472

Deprecation process for legacy permission names

    XMLWordPrintable

Details

    • Task
    • Status: Closed (View Workflow)
    • P3
    • Resolution: Done
    • None
    • None
    • None
    • Core: Platform

    Description

      As described in STRIPES-471, new permission names are defined in all modules, and legacy permissions set up (invisible) that include them while we make the transition. Once we have new VMs that associate diku_admin with the new permissions, I can change their settings guards to the new permissions. Once those modules are in wide use, we can remove diku_admin's association with the legacy permissions from the Ansible scripts; and finally, when that VM is in use, we can remove the old permissions from the modules' package files.

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                mike Mike Taylor
                mike Mike Taylor
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Time Tracking

                    Estimated:
                    Original Estimate - Not Specified
                    Not Specified
                    Remaining:
                    Remaining Estimate - 0 minutes
                    0m
                    Logged:
                    Time Spent - 15 minutes
                    15m

                    TestRail: Runs

                      TestRail: Cases