@adikari We are looking at implementing this for our own purposes. If we can easily create a PR we will link it here for potential inclusion. Is there anything special we need to consider here?

@abdul-ashour is the developer looking into it.

@chrs-myrs first of all thank you for your interest in contributing. The proposed feature will surely help other users so happy to proceed.
Could you share how you are thinking of implementing this feature? Will it be a new optional configuration?

As long as the existing functionality is intact and the feature meets the test threshold requirements, it should be good.

@adikari I will just add an optional config forceCustomNamespace (I am happy to change the option name if you suggest one). If it is set to true and 'namespace' is also set, 'namespace' value will be used rather than the stack-name. Let me know If you have any concern about this approach. I can create the PR by end of today If you are happy with this approach. I am keeping in my mind backward compatibility.

@abdul-ashour sounds good to me. How about we call the option just namespace?

Just to confirm, there is no need in such a case for an additional option as namespace is already there. It will be used If it is set. Otherwise, it will be either the default value or stack-name (depending on whether there is a pattern defined or not).

I created the PR and happy to discuss any requested change.