`newrelic-lambda integrations update` fails to update pre-0.9 stack due to `No newrelic-log-ingestion function in region ...` error

[huonw]

`newrelic-lambda integrations update` fails to update pre-0.9 stack due to `No newrelic-log-ingestion function in region ...` error

[rittneje]

We also encountered this issue. As @huonw mentioned, the error message is completely useless. I'm also very disappointed that it's been almost three months without any solution from New Relic.

I think the decision in v0.9.0 needs to be reversed until New Relic has a valid plan for migrating to the new function name. Also, I will say that adding a suffix to the function seems totally unnecessary. If anything, you should force the other thing to change to get rid of the suffix.

[huonw]

Oh. Maybe this is intended behaviour, according to https://github.com/newrelic/newrelic-lambda-cli/releases/tag/v0.9.0.

If that's the case, how do we update our stacks? Are we stuck on 0.8.0 forever? Maybe there's some method to manually update them, or maybe this script could be upgraded to support the migration automatically?

[chaudharysaket]

Hi @huonw, the new release assumes that one would create a new log-ingestion function with cli version 0.9 and use it for integration.

newrelic-lambda integrations install \
    --nr-account-id <account id> \
    --nr-api-key <api key> \
    --stackname <newrelic-primary-log-ingestion> # sample name for stackname 

The above command would create a new stack with a new log-ingestion-function with some suffix and using same stackname you can subscribe your lambdas.

newrelic-lambda subscriptions install --function <name or arn> --stackname <newrelic-primary-log-ingestion>

Yes, as per the release notes, this change is not compatible with log-ingestion function created with earlier versions. Also could you please indicate what you want to update? Is it the log-ingestion function? Thanks

[huonw]

Thanks for the reply.

We have a stacks we created with newrelic-lambda integrations install --nr-account-id <account id> --nr-api-key <api key> with an old version (by the dates, maybe with v0.7.2 but I don't know for sure). We want to upgrade those stack to the latest version using newrelic-lambda integrations update ..., preferably without any service interruption. (We want to pick up the fix for #248 specifically.)

I tried using 0.9.0 and was getting the errors described in the issue and didn't know the cause, until diving into the code. I'm still somewhat unclear on what the recommended upgrade path is: delete the integration stack and recreate it?

(As a stop gap, I've just used 0.8.0 and that's been enough to resolve the immediate problem.)

As a user, it would've helped me to either have:

1. the 0.9.0 upgrade work without issues
2. if the compatibility break is required, more information about how to upgrade: preferably both of:
   • guidance in the 0.9.0 release notes, it currently says it's unsupported but it could also provide a recommendation for how to resolve the issue
   • the error message itself reference this (e.g. ✖️ No newrelic-log-ingestion-0ab... function in region 'ap-southeast-2'. If you have an stack created with an old version, follow instructions in <link to release notes> to uopgrade; if not, run 'newrelic-lambda integrations install' to install it.)

[chaudharysaket]

We are looking into the ways to make the CLI changes backward compatible. Appreciate the feedback, Thank you!