ENG-48260: Update to fix environment name conflict

[thugrock7]

No description provided.

[tim-mwangi]

So does tme also execute the code to set the default environment when TA_ENVIRONMENT is not set?

[shashank11p]

So does tme also execute the code to set the default environment when TA_ENVIRONMENT is not set?

Yes @tim-mwangi, since tme is basically a smaller tpa without collector! It uses same image and code, just different configs.

[shashank11p]

This also seems like the agentAttributes processor config we have.
Need to think about another name maybe?

[varkey98]

+1

[thugrock7]

Hmm..thought about it while naming. Want to have some thing which specifies this corresponds of parameters specific to an agent (as we may populate it in future). Something like AgentParametersConfig?. I am out of naming ideas tbh.

[varkey98]

How about HostDetails or ServixeDetails ?

[thugrock7]

Should I go with AgentHostAttributes as @varkey98 suggested? Or do you have any suggestions @ryanericson @tim-mwangi @shashank11p @puneet-traceable .

[varkey98]

AgentHostAttributes is also a potential name, I like this better

[tim-mwangi]

So does tme also execute the code to set the default environment when TA_ENVIRONMENT is not set?

Yes @tim-mwangi, since tme is basically a smaller tpa without collector! It uses same image and code, just different configs.

Ok. I see the code in agent.go