-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade to latest New Relic version #1999
Conversation
# | ||
# Kubernetes config: | ||
# https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/ | ||
graceful_timeout = 85 |
Check notice
Code scanning / CodeQL
Unused global variable Note
# Kubernetes config: | ||
# https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/ | ||
graceful_timeout = 85 | ||
timeout = 90 |
Check notice
Code scanning / CodeQL
Unused global variable Note
@@ -20,10 +22,34 @@ | |||
# to be larger than the idle timeout configured for the load balancer. | |||
# > By default, Elastic Load Balancing sets the idle timeout value for your load balancer to 60 seconds. | |||
# https://docs.aws.amazon.com/elasticloadbalancing/latest/application/application-load-balancers.html#connection-idle-timeout | |||
on_aws = os.environ.get("NOTIFY_ENVIRONMENT", "") in ["production", "staging", "scratch", "dev"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know why we fell back on an empty string instead of the default None
value. It seems unnecessary considering the following condition with the AWS env check.
🧪 Review environmenthttps://5l627b5ozouxuu3m3ees2bkxqm0lncbj.lambda-url.ca-central-1.on.aws/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Summary | Résumé
Upgrade to latest New Relic version and bringing additional changes that were performed on the API side.
newrelic.ini
file.fzf
command line utility to the devcontainer along with proper shell config.Test instructions | Instructions pour tester la modification
Check the kubernetes admin pods startup to make sure that these do not get into a crash loop. It is possible we might have to align the admin k8s liveness, readiness and startup probes with the ones in API with their latest changes.