Add wrapper to builder

[ls-urs-keller]

Description

Add the missing builder and query function for the Kind.Wrapper

Issues Resolved

Missing isWrapper, wrapper() and wrapper(...) in a downstream project

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[reta]

Looks like a miss, thank you @ls-urs-keller , could you please add CHANELOG entry?

[ls-urs-keller]

Looks like a miss, thank you @ls-urs-keller , could you please add CHANELOG entry?

Done. What would be the process to get this into the next 2.8.2 version? PR to 2.x branch or back port from main? Thank you.

[reta]

Done. What would be the process to get this into the next 2.8.2 version? PR to 2.x branch or back port from main? Thank you.

Yes, the backport should be automatic but we sadly have DCO failing check :( could you please amend the commit? git --amend --sign-off ? thank you

[opensearch-trigger-bot]

The backport to 2.x failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/backport-2.x
# Create a new branch
git switch --create backport/backport-806-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 550dd4b1e523d4d5d0d1c03104ace317dda4ccb9
# Push it to GitHub
git push --set-upstream origin backport/backport-806-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-2.x

Then, create a pull request where the base branch is 2.x and the compare/head branch is backport/backport-806-to-2.x.

[VachaShah]

Actually I merged this too quickly. This changelog line should be added to the [Unreleased 2.x] section since this is to be released in 2.x. This way, the backport workflow also will not have merge conflicts.

[VachaShah]

@ls-urs-keller Can you manually backport this please? Thank you!

[ls-urs-keller]

@ls-urs-keller Can you manually backport this please? Thank you!

Hey. Yes no problem. So the workflow is:

• decide if something will be back ported before merging to main
• put to the release notes in the corresponding section based on that decision
• manual back port if the decision comes later

What to do with the release notes on the main branch, do I create another PR to correct them, or is this done when 2.x is released?

[ls-urs-keller]

Backport PR #816