#deleting Cloud traces/data
1 messages ยท Page 1 of 1 (latest)
cc @uncut pulsar @viral musk in case this has come up before - sounds legit to me, seems like it would be a simple DELETE in ClickHouse? https://clickhouse.com/docs/en/sql-reference/statements/delete
yes! this is correct, we've done this in the past when some users accidentally leaked sensitve information into their traces. A DELETE in Clickhouse is the way to go indeed Alex ๐
I guess the next question is who is able to trigger this and how. Any org member? Org admin? Delete button on trace page with big warning? Are there downsides to that?
is there a way to somehow group by some kind of id, if its an org account, and we're talking thousands of repos
We would probably not want devs from different teams deleting things there, some kind of way to allocate users to specific modules, or have traces go to a bucket for 'created' teams and then admins of those teams can clear or remove traces but also having an admin of the org account have access to delete traces
sorry, hard to answer, im just trying to think of situations like, how many would be in the org, how do you manage hundreds of repos or just many teams using cloud or something like this. I dont know how it looks
would be cool to somehow have something like "let users who triggered the trace also delete their own traces" or something
Hi, I've just started evaluating Dagger for our team, and we would need some way to remove traces in case someone leaked some sensitive information (could be secrets or some other intellectual property). Is the feature to delete Traces under consideration for implementation?
@spice arrow Yes it is
@idle palm @spice arrow The feature just shipped ๐ข
It's in its most basic form -- org admins have a "Delete trace" button available on each trace
This will really help in getting my organisation to use dagger. We are extremely strict on security. Now when I next dem, I'll be able to answer those in the business and say any security issue found is easily deletable! This is a great feature!
Great to hear! Again, it's in its most basic form right now, but very open to feedback