Resource Modifier Follow-on improvements

[anshulahuja98]

Describe the problem/challenge you have

JSON Merge Patch and Strategic Merge Patch support was added in resource modifier feature through #6917

There are certain follow on improvements which need to be done in following

• E2E test case to cover Strategic/ Merge Patch / GroupResource glob scenarios. https://github.com/vmware-tanzu/velero/tree/main/test/e2e/resourcemodifiers
• Refactor the public docs to a better structuring. https://github.com/vmware-tanzu/velero/blob/main/site/content/docs/main/restore-resource-modifiers.md
• Add unit test case to evaluate and support ~1 based escaping resource-modifier-configmap not applied #6801 (comment)

Describe the solution you'd like

Anything else you would like to add:

Environment:

• Velero version (use velero version):
• Kubernetes version (use kubectl version):
• Kubernetes installer & version:
• Cloud provider or hardware configuration:
• OS (e.g. from /etc/os-release):

Vote on this issue!

This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.

• 👍 for "The project would be better with this feature added"
• 👎 for "This feature will not enhance the project in a meaningful way"

[mailbox171]

Hello,
btw I would like #6801 (comment) to be reopened please

[anshulahuja98]

Hi @mailbox171 it is tracked in this Issue already. I don't understand what you mean by reopening it.

[mailbox171]

#6801 (comment) was about the resource modifier not working.
I added a comment to the Issue: since with the latest version the issues are back, that's what I mean with reopening.

In the same issue there were ALSO some possible improvements mentioned, and that's why is tracked here.

[anshulahuja98]

Will get back in some time.

[arsenalzp]

Hello,
I would like to pick up this issue, however I would like to know is there any deadlines for solving this issue, because I should study this project in details.

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. If a Velero team member has requested log or more information, please provide the output of the shared commands.

[reasonerjt]

Per discussion with @anshulahuja98, I'm moving this out from v1.14 milestone, will keep this in backlog.

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. If a Velero team member has requested log or more information, please provide the output of the shared commands.

[kaovilai]

unstale

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. If a Velero team member has requested log or more information, please provide the output of the shared commands.