Skip to content

Module discovery cmdlets should be able to override PSCompatibleEdition #6992

@rjmholt

Description

@rjmholt

Moving toward broader usage on Windows for PowerShell Core 6, we will need to honour the PSCompatibleEditions field of module manifests.

However, this field may be set conservatively or defaulted to a conservative value. As such we should allow a flag to allow the forced import of those modules for Get-Module [-ListAvailable] and Import-Module.

Ideally the name of this flag should be pithy, expressive about being a compatibility override behaviour, and dangerous-sounding so that users will understand that things may break as a result.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Issue-Enhancementthe issue is more of a feature request than a bugResolution-FixedThe issue is fixed.WG-DevEx-Portabilityauthoring cross-platform or cross-architecture modules, cmdlets, and scriptsWG-Enginecore PowerShell engine, interpreter, and runtime

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions