#6679 add globalConfigurationCustomName parameter

[frantsao]

Proposed changes

Add globalConfigurationCustomName parameter to controller confuguration in helm charts. It is helpful when the GlobalConfiguration is created separately from the helm provisioning, as explained in #6679

Checklist

Before creating a PR, run through this checklist and mark each as complete.

• I have read the CONTRIBUTING doc
• I have added tests that prove my fix is effective or that my feature works
• I have checked that all unit tests pass after adding my changes
• I have updated necessary documentation
• I have rebased my branch onto main
• I will ensure my PR is targeting the main branch and pulling from my branch from my own fork

[github-actions]

✅ All required contributors have signed the F5 CLA for this PR. Thank you!
_{Posted by the CLA Assistant Lite bot.}

[frantsao]

I have hereby read the F5 CLA and agree to its terms

[j1m-ryan]

Hi @frantsao,

I just tested this out, and it works well. Thanks again for working on it. There's one other thing that would be ideal: if the customName and create options could work together.

This would require an update to this file to use the name and namespace parts of the customName, if it exists.

The logic in _helpers.tpl would also need to be adjusted slightly to accommodate this change.

[frantsao]

Hi @frantsao,

I just tested this out, and it works well. Thanks again for working on it. There's one other thing that would be ideal: if the customName and create options could work together.

This would require an update to this file to use the name and namespace parts of the customName, if it exists.

The logic in _helpers.tpl would also need to be adjusted slightly to accommodate this change.

Ok, I think it's a good idea too, but I didn't know if the change could be interesting for you too. I'll work on it as soon as I have some free time again :-)

[j1m-ryan]

Hi @frantsao,
No worries at all, take your time. When you look at this again, you might find that making definitions in _helpers.tpl could be useful for getting the name and namespace defined. You can then use the defintions in the global configuration template file.