Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[EXOTransportRule] Priority parameter is String instead of Int #4136

Closed
ykuijs opened this issue Jan 10, 2024 · 0 comments · Fixed by #4149
Closed

[EXOTransportRule] Priority parameter is String instead of Int #4136

ykuijs opened this issue Jan 10, 2024 · 0 comments · Fixed by #4149
Assignees

Comments

@ykuijs
Copy link
Member

ykuijs commented Jan 10, 2024

Description of the issue

The Priority parameter in the EXOTransportRule resource has been defined in the schema as a String. When reviewing the New-TransportRule cmdlet, there the Priority property is defined as an Int32.

It doesn't sound logical that these are of different types and it would make sense to align these. That would be a breaking change.

Resource schema:

[Write, Description("The Priority parameter specifies a priority value for the rule that determines the order of rule processing.")] String Priority;

New-TransportRule cmdlet: https://learn.microsoft.com/en-us/powershell/module/exchange/new-transportrule?view=exchange-ps

Microsoft 365 DSC Version

Dev

Which workloads are affected

Exchange Online

The DSC configuration

N/A

Verbose logs showing the problem

N/A

Environment Information + PowerShell Version

N/A
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants