Please feel free to provide feedback or file bugs here.

CmdletsToExport publishing issue with large modules

We (the AWS PowerShell Tools team) have hit an issue publishing the AWS modules to the gallery involving a limit of 4000 cmdlets in the CmdletsToExport manifest member. The gallery returns an error when we attempt to publish, which has forced us to revert to using "*-*" in the manifest, which gives a degraded user experience. I inspected the gallery publishing cmdlets and could see no sign of the limit there, so am assuming therefore that this was a gallery-side exception. The limit appears to be isolated to the CmdletsToExport manifest member as we're able to publish the module with the change even though it contains a large number of cmdlets.

We have backlog work queued to break our module into multiple sub-modules. In the meantime we're looking for a fix or workaround that will enable us to re-start publishing our module to the gallery and have all cmdlets listed in the manifest.

Can anyone offer any suggestions or fixes?

1 vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Steve Roberts shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    2 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • Edyoung-MSFT commented  ·   ·  Flag as inappropriate

        We will raise the limit to 5000 in the next update, likely this week. We do still recommend dividing into multiple modules - there are plenty of other places in the gallery and in powershell itself where a large number of commands in one module may be a usability issue.

      Feedback and Knowledge Base