Question or feature request: Why we can't use service name instead of GUID?

[vitalykarasik]

The action requests "The entity GUID to apply the deployment marker" for each deploy event. It means I have to collect a list of GUIDs for all services across all environments and use them in my workflow.

But we already have a 'service name' in both NewRelic and GH workflow. So why don't use it instead of GUID for calling this action?

[oleksandr-kinship]

@vitalykarasik have you got any answer? have the same question, +1

[vitalykarasik]

@vitalykarasik have you got any answer? have the same question, +1

@oleksandr-kinship unfortunately, no. I'm just adding GUID for each service into its CI/CD workflow - hardcoded :-(

[oleksandr-kinship]

@vitalykarasik have you got any answer? have the same question, +1

@oleksandr-kinship unfortunately, no. I'm just adding GUID for each service into its CI/CD workflow - hardcoded :-(

That upset to have to use antipatterns. Thanks. for quick answer!

[oleksandr-kinship]

Hello @vitalykarasik, bit think about how it could be integrated without minimal hardcode for big amount of applications, so I think I have found the most straightforward solution - write reusable action that will call NR api to get guid first, then use this output in deployment marker arguments. As base for get_uid can be used this action, just use another cli call

newrelic apm application search \
            --name ${NEW_RELIC_APM_NAME}

then this possible to grep/jq guid from response.