Table: github_actions_artifact - Query GitHub Actions Artifacts using SQL
GitHub Actions Artifacts are the files created when you build and test your code. These artifacts allow you to persist data after a job has completed, and share that data with another job in the same workflow. An artifact can be a compile output, a log file, a test result, or any other data you want to preserve or share.
Table Usage Guide
The github_actions_artifact
table provides insights into artifacts generated by GitHub Actions workflows. As a software developer or DevOps engineer, explore artifact-specific details through this table, including metadata and download URLs. Utilize it to uncover information about artifacts, such as their size, download location, and associated workflow runs.
Important Notes
- You must specify the
repository_full_name
column inwhere
orjoin
clause to query the table.
Examples
List artifacts
Explore which artifacts are associated with the 'turbot/steampipe' repository on GitHub. This can be useful for developers needing to understand or manage the resources related to this specific project.
select *from github_actions_artifactwhere repository_full_name = 'turbot/steampipe';
select *from github_actions_artifactwhere repository_full_name = 'turbot/steampipe';
List active artifacts
Discover the segments that are active artifacts within a specific repository, which is useful in scenarios where you need to track and manage these artifacts for ongoing projects or maintenance tasks. This query enables you to focus on active artifacts, excluding those that have expired, to streamline your artifact management process.
select id, node_id, name, archive_download_url, expiredfrom github_actions_artifactwhere repository_full_name = 'turbot/steampipe' and not expired;
select id, node_id, name, archive_download_url, expiredfrom github_actions_artifactwhere repository_full_name = 'turbot/steampipe' and not expired;
Schema for github_actions_artifact
Name | Type | Operators | Description |
---|---|---|---|
_ctx | jsonb | Steampipe context in JSON form. | |
archive_download_url | text | Archive download URL for the artifact. | |
created_at | timestamp with time zone | Time when the artifact was created. | |
expired | boolean | It defines whether the artifact is expires or not. | |
expires_at | timestamp with time zone | Time when the artifact expires. | |
id | bigint | = | Unique ID of the artifact. |
login_id | text | =, !=, ~~, ~~*, !~~, !~~* | Unique identifier for the user login. |
name | text | The name of the artifact. | |
node_id | text | Node where GitHub stores this data internally. | |
repository_full_name | text | = | Full name of the repository that contains the artifact. |
size_in_bytes | bigint | Size of the artifact in bytes. | |
sp_connection_name | text | =, !=, ~~, ~~*, !~~, !~~* | Steampipe connection name. |
sp_ctx | jsonb | Steampipe context in JSON form. |
Export
This table is available as a standalone Exporter CLI. Steampipe exporters are stand-alone binaries that allow you to extract data using Steampipe plugins without a database.
You can download the tarball for your platform from the Releases page, but it is simplest to install them with the steampipe_export_installer.sh
script:
/bin/sh -c "$(curl -fsSL https://steampipe.io/install/export.sh)" -- github
You can pass the configuration to the command with the --config
argument:
steampipe_export_github --config '<your_config>' github_actions_artifact