feat: Add UDT to avm/res/operational-insights/workspace

[krbar]

Description

Add User Defined Types to the Log Analytics Workspace module.
Also fixes #3798

Pipeline Reference

Pipeline

Type of Change

• Update to CI Environment or utilities (Non-module affecting changes)
• Azure Verified Module updates:
  • Bugfix containing backwards-compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in version.json:
    • Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description.
    • The bug was found by the module author, and no one has opened an issue to report it yet.
  • Feature update backwards compatible feature updates, and I have bumped the MINOR version in version.json.
  • Breaking changes and I have bumped the MAJOR version in version.json.
  • Update to documentation

Checklist

• I'm sure there are no other open Pull Requests for the same update/change
• I have run Set-AVMModule locally to generate the supporting module files.
• My corresponding pipelines / checks run clean and green without any errors or warnings

[AlexanderSehr]

Suggested change

	metaData: destinationMetaDataType?
	}
	@export()
	type destinationMetaDataType = {
	@description('Optional. Allows to define an Event Hub name. Not applicable when destination is Storage Account.')
	eventHubName: string?
	}
	metaData: {
	@description('Optional. Allows to define an Event Hub name. Not applicable when destination is Storage Account.')
	eventHubName: string?
	}?
	}

If only used in one location why 2 types?

[AlexanderSehr]

If you want to adopt this suggestion, the same comment applies to all other types. If not, nevermind. 😄

[krbar]

I merged these two types into one, but somehow I overlooked your commitable suggestion and made the same change on my own.... 🤷‍♂️

[jtracey93]

Hey @krbar ,

Firstly, thanks for your work on this PR!

We have made some changes to the AVM CI, detailed below, which means we need you to update your fork to pull in these latest changes and re-run your tests to show they still are passing prior to approving and merging this PR, as we don't and it fails once merged the publishing of your module will fail and will be blocked going forward until the test pass again via additional PRs.

Changes to CI That Have Been Made That You Need To Take Action On

• feat: Add WAF Security PS Rule Config #3745
  • Adds WAF Security PSRule Checks using this custom baseline of rules (/avm/utilities/pipelines/staticValidation/psrule/.ps-rule/cb-waf-security.Rule.yaml)
  • Action Required By You:
    • Ingest/pull-in these changes into your PR branch and re-run your tests to ensure they pass
      • If any issues with the rules and you think it should apply, please ping/reach out to the core team

Any questions reach out to the AVM Core Team by tagging us in your PR here or internally via Teams

Thanks

Jack (AVM Core Team)

[krbar]

Thanks @jtracey93 the PR is updated and the module passes the validation. There was also an update of Bicep so the README/ARM files had to be re-generated too.