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

Correct typos in resource names #3024

Closed
ykuijs opened this issue Mar 16, 2023 · 0 comments · Fixed by #3106 or #3140
Closed

Correct typos in resource names #3024

ykuijs opened this issue Mar 16, 2023 · 0 comments · Fixed by #3106 or #3140
Assignees
Labels
Breaking Changes Bug Something isn't working Intune

Comments

@ykuijs
Copy link
Member

ykuijs commented Mar 16, 2023

Details of the scenario you tried and the problem that is occurring

The following resources have typos in them. These should be corrected, but will be a breaking change:

  • IntuneWifiConfigurationPolicyAndroidEntrepriseDeviceOwner: Entreprise should be Enterprise
  • IntuneWifiConfigurationPolicyAndroidEntrepriseWorkProfile: Entreprise should be Enterprise
  • IntuneWindowUpdateForBusinessRingUpdateProfileWindows10: Window should be Windows

Verbose logs showing the problem

N/A

Suggested solution to the issue

Fix typo

The DSC configuration that is used to reproduce the issue (as detailed as possible)

N/A

The operating system the target node is running

N/A

Version of the DSC module that was used ('dev' if using current dev branch)

dev

@ykuijs ykuijs added Bug Something isn't working Breaking Changes labels Mar 16, 2023
@ykuijs ykuijs changed the title Typo in resource names Correct typos in resource names Mar 16, 2023
@ykuijs ykuijs self-assigned this Mar 19, 2023
@ykuijs ykuijs added the Intune label Mar 19, 2023
ykuijs added a commit that referenced this issue Mar 31, 2023
[BREAKING CHANGE] Fixed #3024 and #3075
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Breaking Changes Bug Something isn't working Intune
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant