Config document resource schema is missing additionalProperties true

[ThomasNieto]

The resource section of the config document does not prevent additional properties from being added.

resources:
- name: test
  type: Microsoft.Windows/Registry
  myRandomProperty: should not be here!
  properties:
    keyPath: HKCU\test
    valueName: abc
    valueData:
     String: def

Original issue about versioning but is duplicate

Summary of the new feature / enhancement

As a user I want to be able to specify which version or version range of a resource I want to use. Then when running the configuration document if the resource version is not present error.

Proposed technical implementation details (optional)

type: owner[.group][.area]/name@1.2.3
name: instance_name
properties:
  propertyName: propertyValue

NuGet range syntax

type: owner[.group][.area]/name@[1.0,2.0)
name: instance_name
properties:
  propertyName: propertyValue

[SteveL-MSFT]

In the YAML, you would need to specify it as the version or apiVersion property, but in Bicep, it would take the @version syntax

[ThomasNieto]

The schema for config document doesn't show anything about a version or apiVersion property. Adding version doesn't throw an error is the resource version doesn't exist. Also, this may have revealed a bug in the schema file where it doesn't set additionalProperties to false.

resources:
- name: test
  type: Microsoft.Windows/Registry
  version: 0.2.0
  properties:
    keyPath: HKCU\test
    valueName: abc
    valueData:
     String: def

[SteveL-MSFT]

@ThomasNieto I thought I had made the change to add apiVersion to the schema, but I guess I had not yet. You're right that additionalProperties should be false

This is all waiting on #543 to get implemented

[ThomasNieto]

@SteveL-MSFT going to rename this issue to be about the additionalProperties since the original issue is a duplicate of #543