Closed Brendmanitix closed 8 months ago
On closer inspection, it looks like the suffix is the AWS::StackId
It appears to be a deliberate change to the aws-log-ingestion
template:
https://github.com/newrelic/aws-log-ingestion/commit/de0271fc55a9abf13a34c09e8b24d23e0127c05a
🤷♂️
I've filled an internal bug report on this to get this onto our roadmap and fix it.
Description
Running
newrelic-lambda integrations install -e ...
completes successfully, but the NewRelicLogIngestionFunction in the NewRelicLogIngestion stack has an id suffixnewrelic-log-ingestion-0a20eba5a086
which causes subsequent commands to fail. When I first ran install, I got this error message telling me to remove the existing lambda and re-installing. https://github.com/newrelic/newrelic-lambda-cli/blob/3e56f005af4ccb4328b282886894e5f42a8c8328/newrelic_lambda_cli/integrations.py#L565.or
Steps to Reproduce
newrelic-log-ingestion
function that was not part of a CloudFormation stacknewrelic-lambda integrations install -e [...]
newrelic-lambda integrations update [...]
No 'newrelic-log-ingestion' function in region 'ap-southeast-2
newrelic-lambda integrations uninstall
Expected Behaviour
Commands should find installed log ingestion function and perform updates, etc.
Relevant Logs / Console output
Other stack resources, in case that's useful. They all appear to have a suffix.