Actions
/
digikey-search-html-report
mirror of https://github.com/AllSpiceIO/digikey-search-html-report.git
6
Fork 0
Files Issues Releases Activity
An AllSpice Actions add-on for DigiKey API search and HTML report generation given an input BOM
27 Commits 2 Branches 3 Tags 2.8 MiB
Python 57.5%
HTML 41.8%
Dockerfile 0.7%
Go to file
Kyle Dumont 6cb38f6c7d
Merge pull request #8 from AllSpiceIO/develop 
Fix CI and Update README
 		2024-09-05 15:22:23 -04:00
.github update actions triggers 2024-09-05 10:40:46 -04:00
report_template Minor color fix in HTML 2024-09-03 10:06:47 -05:00
.gitignore Initial commit of feature-complete v1 version 2024-07-09 10:38:22 -05:00
Dockerfile Initial commit of feature-complete v1 version 2024-07-09 10:38:22 -05:00
LICENSE Initial commit 2024-07-08 15:23:09 -05:00
README.md Fix version ref in README 2024-09-05 10:34:41 -04:00
action.yml Initial commit of feature-complete v1 version 2024-07-09 10:38:22 -05:00
entrypoint.py Fix formatting 2024-09-05 10:36:54 -04:00
pyproject.toml Initial commit of feature-complete v1 version 2024-07-09 10:38:22 -05:00
requirements-test.txt Bump ruff from 0.4.7 to 0.6.3 2024-09-01 18:40:19 +00:00
requirements.txt Initial commit of feature-complete v1 version 2024-07-09 10:38:22 -05:00

README.md

DigiKey-Search-HTML-Report

An actions repository for demonstrating DigiKey API integration and HTML report generation given an input BOM

This action uses the DigiKey API. See the DigiKey API docs for more information.

Usage

Add the following step to your actions:

- name: Generate HTML component report using DigiKey API
  uses: https://hub.allspice.io/Actions/digikey-search-html-report.git@v3
  with:
    bom_file: bom.csv
    digikey_client_id: ${{ secrets.DIGIKEY_CLIENT_ID }}
    digikey_client_secret: ${{ secrets.DIGIKEY_CLIENT_SECRET }}

This add-on requires the DigiKey client ID and client secret to be stored as Actions secrets. Refer to the knowledge base article on Actions secrets to learn how to add the required secrets to your repository.

Input BOM

The input BOM to this Action is assumed to be generated from the py-allspice BOM generation utility. The column names referenced and used in this Action script assume the naming convention as populated by the py-allspice BOM generation function. The user is to adjust the expected column positions and naming conventions when using their own BOM file input.

A typical workflow is to use the BOM generation Actions add-on to generate the BOM first, and use the generated BOM as an input to this Action.