LOG-8007: Make AzureMonitor LogType a required, non-empty field

[vparfonov]

Description

The LogType field in AzureMonitor Output specification was previously incorrectly allowed an empty string ("") as a valid value. This leads to failing Vector collector with:
2025-10-24T08:42:56.862842Z ERROR vector::topology::builder: Configuration error. error=Sink "output_abc_azure": invalid log_type "": log type can only contain letters, numbers, and underscore (_), and may not exceed 100 characters

This PR makes the field mandatory and non-empty by:

1. Adding +kubebuilder:validation:Required to ensure the key is present.
2. Adding +kubebuilder:validation:MinLength:=1 to reject empty values.
3. Removing omitempty from the JSON tag to prevent controller reconciliation errors.

/cc @Clee2691 @cahartma
/assign @jcantrill

Links

• Depending on PR(s):
• GitHub issue:
• JIRA: https://issues.redhat.com/browse/LOG-8007
• Enhancement proposal:

[openshift-ci-robot]

@vparfonov: This pull request references LOG-8007 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.8.0" version, but no target version was set.

In response to this:

Description

The LogType field in AzureMonitor Output specification was previously incorrectly allowed an empty string ("") as a valid value. This leads to failing Vector collector with:
2025-10-24T08:42:56.862842Z ERROR vector::topology::builder: Configuration error. error=Sink "output_abc_azure": invalid log_type "": log type can only contain letters, numbers, and underscore (_), and may not exceed 100 characters

This PR makes the field mandatory and non-empty by:

1. Adding +kubebuilder:validation:Required to ensure the key is present.
2. Adding +kubebuilder:validation:MinLength:=1 to reject empty values.
3. Removing omitempty from the JSON tag to prevent controller reconciliation errors.

/cc @Clee2691 @cahartma
/assign @jcantrill

Links

• Depending on PR(s):
• GitHub issue:
• JIRA: https://issues.redhat.com/browse/LOG-8007
• Enhancement proposal:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[vparfonov]

/test unit

[vparfonov]

/assign @jcantrill

[jcantrill]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jcantrill, vparfonov

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [jcantrill]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@vparfonov: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.