Details

    • Type: Sub-task
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 5.3.4, PUP 5.4.0, PUP 5.5.3
    • Component/s: Modules
    • Labels:
      None
    • Template:
    • Acceptance Criteria:
      Hide

      Module translations show up during an agent run and when using puppet's CLI applications.

      Show
      Module translations show up during an agent run and when using puppet's CLI applications.
    • Team:
      Platform Core
    • Sprint:
      Platform Core KANBAN
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      Puppet will now correctly load module translations on both the agent and the server.
    • QA Risk Assessment:
      No Action

      Description

      Currently we are naively loading modules' translations whenever a Ruby instance of the Module class is created, in a way assumes that the locale files are located within the module's installed directory. This works on the master and when doing things like puppet apply, but agent runs get their data from $vardir, which is populated by pluginsync. We need to add hooks to load module translations from $vardir after pluginsyncing, and make sure we check both places (installed modules and $vardir) when invoking puppet applications, to ensure we get translations when and where we need them. This ticket mostly entails getting correct translation behavior, over optimizing, which is covered in PUP-8024.

        Attachments

          Activity

            jsd-sla-details-panel

              People

              • Assignee:
                maggie Maggie Dreyer
                Reporter:
                maggie Maggie Dreyer
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Zendesk Support