feat(onelake_shortcut): onboard new data-source and resource

[catalina-gav]

📥 Pull Request

❓ What are you trying to address

close #422
close #421

Onboard new onelake shortcut resource/data-source

[github-actions]

Changelog Preview

v1.2.1-dev - June 13, 2025

✨ Added

• #421 Onboard new fabric_onelake_shortcut data source
• #422 Onboard new fabric_onelake_shortcut resource
• #453 new ephemeral resource fabric_eventstream_source_connection
• #491 new data-source fabric_eventstream_source_connection

💫 Changed

• #471 Removed preview for fabric_gateway
• #472 Removed preview for fabric_gateway_role_assignment

[OrBaubergMicrosoft]

can you move validations that only one is populated to here?

[catalina-gav]

@DariuszPorowski I'm trying to move a validation rule from the ConfigValidators section in resource_shortcut.go into the schema definition using objectvalidator.ExactlyOneOf. Specifically, I’ve replaced the original resourcevalidator.ExactlyOneOf(...) with this schema-level code:

Validators: []validator.Object{
    objectvalidator.ExactlyOneOf(
        path.MatchRelative().AtName("onelake"), //tried with matchRoot as it was in ConfigValidators too
        path.MatchRelative().AtName("adls_gen2"),
        path.MatchRelative().AtName("amazon_s3"),
        ...
    ),
},

I’ve seen similar usage with validators like RequireIfAttributeIsOneOf and NullIfAttributeIsOneOf, which work correctly inside the schema. However, after switching to objectvalidator.ExactlyOneOf, I'm seeing unexpected behavior during unit tests: the cases that previously passed using resourcevalidator.ExactlyOneOf now fail with the new schema validation.

I was wondering if we can even move this validation ConfigValidators to schema-level, and if so, any guidance on the correct usage or how to structure this validation inside the schema would be much appreciated. Thanks!