Changing collector name creates duplicate credentials in sumologicextension #42511
Description
Component(s)
exporter/sumologic
Describe the issue you're reporting
The sumologicextension currently uses the collector name as part of the credential path hash key. This causes a major problem:
Whenever the collector name is updated, a new credential path is generated.
This results in duplicate credentials being created, which results in registration of collector that cause name/id change.
As a side effect, renaming a collector is not possible without re-provisioning collector name or id.
We want to give user freedom to change name without re-registration of the collector
### Proposed Change
Remove the collector name from the credential path key calculation. Credentials should be keyed only on the actual authentication data, so that changing the collector name does not create new, unnecessary credentials.
Risks / Considerations
Users with existing collector-name–specific credential paths may need to migrate or re-store credentials after upgrading.
Backward compatibility must be clearly documented.
Tip
React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.