Feature request: Allow same name on different data input

[ejosesentia]

Description

Hi,

I have created two input services, but when I try to create the same name on both I get a Name already used error. This should not be an issue since they will have different service names.

What UCC version are you using?

splunk_add_on_ucc_framework=5.49.0

Additional System Info

Python 3.9, Linux

[hetangmodi-crest]

Hi @ejosesentia, the same name error occurs due to the following reasons:

• acts as a safety net where developers use the input name to create and maintain the checkpoints, creating input specific log files.
• if there are 2+ inputs with the same name, it would be confusing for the add-on user which input is of which service unless the service name isn't explicitly mentioned in table view.

Can you please share a specific use case where having 2 or more inputs with same name but of different input services serving a good purpose and user experience to add-on users?

[ejosesentia]

Hi @hetangmodi-crest,

In my case I am collecting data from different service end points on the same app running on multiple servers. I use different data inputs for each of the service. Since I am collecting the same data where the only difference is the server hosting it, it is better to use the hostname of the server when naming the data input. When I first experienced this, I was surprised because I was expecting that it is possible to use the same name on a different data input.

I think developers that will create multiple inputs that creates checkpoints would already consider having a unique checkpoint for each of the data input. This would already be an issue that will occur during development.

As for the add-on user. I think that it will not be an issue, since they will still need to select which data input they are setting up and each data input. It will be up to the developer to add the service name in the table view or even better use the "Tab view" which would display each of the data input in different tables.

After thinking about it. This would be a feature request not a bug.

[hetangmodi-crest]

Okay, in that case, I'll just update the summary and labels for the feature request.