Skip to content
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

Access control per baggage item key #2

Open
ktoso opened this issue Sep 25, 2020 · 2 comments
Open

Access control per baggage item key #2

ktoso opened this issue Sep 25, 2020 · 2 comments
Assignees

Comments

@ktoso
Copy link
Member

ktoso commented Sep 25, 2020

This mirrors the slashmo/gsoc-swift-baggage-context#35 ticket

--

Additional capability similar to privacy in os_log to be added to baggage keys.

A key has to define if it wants to be included in forEach and if it wants to be logged.

[...] mark a key as containing sensitive information . for example, you may have a key that carries sensitive user information and that you never want the collectors to log

via @tomerd

@ktoso ktoso self-assigned this Sep 25, 2020
@ktoso
Copy link
Member Author

ktoso commented Sep 25, 2020

Existing PR on old repo ktoso/gsoc-swift-baggage-context#2

@weissi
Copy link
Member

weissi commented Dec 16, 2022

This could be handled with static properties on the keys, right? We can default them to true but if you don't want them to be logged/enumerated/... you set them to false. Something like static var allowsEnumeration: Bool { return false }

@ktoso ktoso modified the milestones: 1.0.0, 1.1.0 May 26, 2023
@ktoso ktoso removed this from the 1.1.0 milestone Jul 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants