As an organization we want to instrument each lambda, but have thousands of lambdas. Having to maintain a list of variables needed for the DT lambda layer on each lambda creates a lot of tech debt any time there is a new layer.
Is it on the roadmap to be able to provide the name of an AppConfig that the settings are stored in as the environment variable and the DT layer loads from there when your Wrapper Script /opt/dynatrace (defined in AWS_LAMBDA_EXEC_WRAPPER) runs?
Otherwise I may have to do this, which has its own drawbacks:
- Add AWS App Config Extension and have it pre-load the variables
- Add my own custom layer that will map those variables to environment variables
- Will have to set AWS_LAMBDA_EXEC_WRAPPER to my custom Wrapper Script /opt/map-app-config-to-env-vars
- My script will then have to know to invoke your script at /opt/dynatrace.
- DT lambda layer script
I've also got a ticket open with AWS to get their recommendations on how to orchestrate the wrapper scripts so mine runs, then dynatrace, then the lambda is invoked.
Thoughts??
