Annotation on a DSC Resource regarding elevation requirements about dsc

[denelon]

Ideally, this would be supported for both DSC v2 PowerShell Class based resources and DSC v3 resources.

[michaeltlombardi]

A few approaches spring to mind for DSCv3 resources, all in the resource manifest:

1. Add an elevation property to the top-level of the manifest, with the enum values default, prohibited, required, and self - the expectation here is that the resource executes according to this setting, regardless of the operation. So if a resource is defined with "elevation": "required", it must be run elevated for get, test, and set operations. If the property isn't specified, the resource is interpreted as having a value of default.
2. Add the same property to the command/operation sections of the manifest. In this case, the property applies only to that operation. Setting elevation for set has no effect on whether elevation is required or prohibited for get.

I think it would be possible to support both, but only one in a manifest - if the top-level elevation is set it should be prohibited in the operation properties and vice versa.

I don't see a way to do this for existing PSDSC resources, short of introducing a new attribute (like DscElevation()) or a not-required method, like GetElevationInfo(). It can't be worked backwards into the existing DscResource() attribute as far as I know.

[SteveL-MSFT]

Fixed via #351