Initially made using Chrome Extension Boilerplate with React 17 and Webpack 5
Note:
While I use this extension every day, I still consider it a "toy" project since it's a first time creating a chrome extension and a first webpack/react project.
This extension let's you monitor your ArgoCD applications:
- By showing applications status (Health and Sync)
- By notifying on status change
- Show the status directly on the browser (if the extension is pinned)
For this it only a required an Argo CD access token with read-only rights to applications.
More information:
- On ArgoCD API Docs: https://argo-cd.readthedocs.io/en/stable/developer-guide/api-docs/
- On Argo CD User Management and RBAC Rules
- Check if your Node.js version is >= 16.
- Clone this repository.
- Run
npm install
to install the dependencies. - Run
npm start
- Load your extension on Chrome following:
- Access
chrome://extensions/
- Check
Developer mode
- Click on
Load unpacked extension
- Select the
build
folder.
- Access
- Happy hacking.
After the development of your extension run the command
$ NODE_ENV=production npm run build
Now, the content of build
folder will be the extension ready to be submitted to the Chrome Web Store. Just take a look
at the official guide to more infos about publishing.
If you are developing an extension that talks with some API you probably are using different keys for testing and production. Is a good practice you not commit your secret keys and expose to anyone that have access to the repository.
To this task this boilerplate import the file ./secrets.<THE-NODE_ENV>.js
on your modules through the module named
as secrets
, so you can do things like this:
./secrets.development.js
export default {key: '123'};
./src/popup.js
import secrets from 'secrets';
ApiCall({key: secrets.key});
👉 The files with name secrets.*.js
already are ignored on the repository.