The Export-ODataEndpointProxy cmdlet uses the metadata of an OData endpoint to generate a module
that contains cmdlets you can use to manage that OData endpoint. The module is based on CDXML. After
this cmdlet generates the module, it saves that module to the path and file name specified by the
OutputModule parameter.
Export-ODataEndpointProxy generates cmdlets for create, read, update, and delete (CRUD)
operations, non-CRUD actions, and association manipulation.
Export-ODataEndpointProxy generates one CDXML file per endpoint resource. You can edit these CDXML
files after the module is generated. For example, if you want to change the noun or verb names of
the cmdlets to align with Windows PowerShell cmdlet naming guidelines, you can modify the file.
Every cmdlet in a generated module must include a ConnectionURI parameter in order to connect to
the endpoint that the module manages.
Examples
Example 1: Generate a module to manage a retail web service endpoint
This command generates a module to manage a retail service endpoint. The command specifies the URI
of the endpoint and the URI of the endpoint metadata. The command also provides an output path and
script module name as the value of the OutputModule parameter. For the value of the
ResourceNameMapping parameter, the command provides a hashtable that maps the resource
collection name to the desired noun for the cmdlet set. In this example, Products is the resource
collection name and Merchandise is the noun. To allow connections to non-SSL sites, HTTP, as
opposed to HTTPS, add the AllowUnsecureConnection parameter.
Parameters
-AllowClobber
Indicates that this cmdlet replaces an existing module.
Specifies a user account that has access to the OData endpoint. The default value is the current
user. If a remote computer runs Windows Vista or a later release of the Windows operating system,
the cmdlet prompts you for credentials.
Specifies the path and module name to which this cmdlet saves the generated module of proxy
commands.
This cmdlet copies a binary module, module manifest, and formatting file, if applicable, to the
specified folder. If you specify only the name of the module, Export-ODataEndpointProxy saves the
module in the $HOME\Documents\WindowsPowerShell\Modules folder. If you specify a path, the cmdlet
creates the module folder in that path.
Specifies a hashtable that contains mappings that let you customize the generated cmdlets. In this
hashtable, the resource collection name is the key. The desired cmdlet noun is the value.
For example, in the hash table @{Products = 'Merchandise'}, Products is the resource
collection name that serves as the key. Merchandise is the resulting cmdlet noun. The generated
cmdlet names might not align to Windows PowerShell cmdlet naming guidelines. You can modify the
resource CDXML file to change the cmdlet names after this cmdlet creates the module. For more
information, see
Strongly Encouraged Development Guidelines.
This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable,
-InformationAction, -InformationVariable, -OutBuffer, -OutVariable, -PipelineVariable,
-ProgressAction, -Verbose, -WarningAction, and -WarningVariable. For more information, see
about_CommonParameters.
The source for this content can be found on GitHub, where you can also create and review issues and pull requests. For more information, see our contributor guide.