issue_comments
5 rows where "created_at" is on date 2022-09-22 sorted by node_id
This data as json, CSV (advanced)
Suggested facets: reactions, updated_at (date)
issue 2
id | html_url | issue_url | node_id ▼ | user | created_at | updated_at | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
1255603780 | https://github.com/simonw/datasette/issues/1415#issuecomment-1255603780 | https://api.github.com/repos/simonw/datasette/issues/1415 | IC_kwDOBm6k_c5K1v5E | bendnorman 17532695 | 2022-09-22T22:06:10Z | 2022-09-22T22:06:10Z | NONE | This would be great! I just went through the process of figuring out the minimum permissions for a service account to run
The Viewer Role is a Basic IAM role that Google does not recommend using:
If you don't grant the Viewer role the ``` ERROR: (gcloud.builds.submit) The build is running, and logs are being written to the default logs bucket. This tool can only stream logs if you are Viewer/Owner of the project and, if applicable, allowed by your VPC-SC security policy. The default logs bucket is always outside any VPC-SC security perimeter.
If you want your logs saved inside your VPC-SC perimeter, use your own bucket.
See https://cloud.google.com/build/docs/securing-builds/store-manage-build-logs.
You can store Cloud Build logs in a user-created bucket which only requires the Storage Admin role. However, you have to pass a config file to I propose we add an additional CLI option to |
{ "total_count": 1, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 1, "eyes": 0 } |
feature request: document minimum permissions for service account for cloudrun 959137143 | |
1255332217 | https://github.com/simonw/sqlite-utils/issues/358#issuecomment-1255332217 | https://api.github.com/repos/simonw/sqlite-utils/issues/358 | IC_kwDOCGYnMM5K0tl5 | simonw 9599 | 2022-09-22T17:27:34Z | 2022-09-22T17:27:34Z | OWNER | I've been thinking about this more recently. I think the first place to explore these will be in the Relevant docs: https://www.sqlite.org/lang_createtable.html#check_constraints
Something like this:
Where Then can bundle a bunch of other pre-baked recipes, but also support the following:
The besign reason for the Detecting |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Support for CHECK constraints 1082651698 | |
1255333969 | https://github.com/simonw/sqlite-utils/issues/358#issuecomment-1255333969 | https://api.github.com/repos/simonw/sqlite-utils/issues/358 | IC_kwDOCGYnMM5K0uBR | simonw 9599 | 2022-09-22T17:29:09Z | 2022-09-22T17:29:09Z | OWNER | Quick demo of a check constraint for JSON validation:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Support for CHECK constraints 1082651698 | |
1255341690 | https://github.com/simonw/sqlite-utils/issues/358#issuecomment-1255341690 | https://api.github.com/repos/simonw/sqlite-utils/issues/358 | IC_kwDOCGYnMM5K0v56 | simonw 9599 | 2022-09-22T17:35:23Z | 2022-09-22T17:35:23Z | OWNER | Make me think also that |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Support for CHECK constraints 1082651698 | |
1255340974 | https://github.com/simonw/sqlite-utils/issues/358#issuecomment-1255340974 | https://api.github.com/repos/simonw/sqlite-utils/issues/358 | IC_kwDOCGYnMM5K0vuu | simonw 9599 | 2022-09-22T17:34:45Z | 2022-09-22T17:34:45Z | OWNER | A few other recipes off the top of my head:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Support for CHECK constraints 1082651698 |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE [issue_comments] ( [html_url] TEXT, [issue_url] TEXT, [id] INTEGER PRIMARY KEY, [node_id] TEXT, [user] INTEGER REFERENCES [users]([id]), [created_at] TEXT, [updated_at] TEXT, [author_association] TEXT, [body] TEXT, [reactions] TEXT, [issue] INTEGER REFERENCES [issues]([id]) , [performed_via_github_app] TEXT); CREATE INDEX [idx_issue_comments_issue] ON [issue_comments] ([issue]); CREATE INDEX [idx_issue_comments_user] ON [issue_comments] ([user]);
user 2