You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 22, 2022. It is now read-only.
Yeah, that's fine. If it's possible to not emit a CLI arg in the case that the config doesn't specify :tracing, that would relax the requirement that all users have to update their CLI. Not the end of the world either way.
I understand your issue with not emitting --tracing-config when it's not specified, but on the other side, it will create synchronization & comparison mess in local vs remote comparison -> fire or not fire update-function-configuration. I'd rather fire it always. This is the same issue as it was with VPC, devs were forced to update awscli to use VPC. I don't see it as an issue, but your project, decide ;-)
There's new switch in the awscli for update-function-configuration:
It's AWS X-Ray related and I would like to add support for it. Proposal is:
:tracing
can be used in:defaults
and per lambda function:tracing
values can be:active
or:passthrough
:tracing
is not provided, it defaults to:passthrough
It defaults to
:passthrough
, because it's a default value for all AWS Lambda functions (checked via awscli).Okay?
The text was updated successfully, but these errors were encountered: