5 Commits

Author SHA1 Message Date
Stas Schaller 5dd14e97cd fix: exclude internal dev files from Docker image and git tracking
- Add .claude/, CLAUDE.md, and non-README *.md to .dockerignore to
  prevent internal tooling files from being included in published image
- Add .claude/ to .gitignore to prevent accidental commits of local config
- Add dockerhub-overview.md for Docker Hub repository description
2026-04-24 14:12:29 -04:00
stas-schaller b4383cf712 Merge pull request #6 from Keeper-Security/release/v1.0.0
Release/v1.0.0
2026-03-03 12:17:12 -05:00
stas-schaller 721adbcbc3 Fix workflow and prepare for Docker Hub publishing (#4)
* fix: commit package-lock.json for reproducible Docker builds

- Remove package-lock.json from .gitignore (was incorrectly ignored)
- Add package-lock.json with pinned dependency versions
- Use npm ci for faster, deterministic installs in CI
- Re-enable npm cache for build performance
- Ensures exact dependency versions in Docker images

* fix: remove unused catch parameter

* docs: update Docker image name to official keeper/harness-plugin

- Replace placeholder dhborse/keeper-harness-plugin with keeper/harness-plugin:latest
- Use official Keeper organization image name
2026-02-16 14:14:49 -05:00
Stas Schaller 65515eb4d9 fix: remove npm cache from workflow (package-lock.json is gitignored) 2026-02-16 11:52:36 -05:00
pkamble-ks 74636825f9 Merge pull request #2 from Keeper-Security/release/v1.0.0
Release/v1.0.0
2026-02-13 22:39:31 +05:30
6 changed files with 4539 additions and 3 deletions
+9
View File
@@ -30,3 +30,12 @@ build/
tmp/
temp/
*.tmp
# Claude Code files - internal dev tooling, never ship in image
.claude/
CLAUDE.md
plans/
# Documentation files not needed at runtime
*.md
!README.md
-1
View File
@@ -239,7 +239,6 @@ jobs:
uses: actions/setup-node@v4
with:
node-version: '20.x'
cache: 'npm'
- name: Get version
id: get_version
+1 -1
View File
@@ -1,2 +1,2 @@
node_modules/
package-lock.json
.claude/
+21
View File
@@ -0,0 +1,21 @@
# Keeper Secrets Manager Harness Plugin
Retrieve secrets from Keeper Vault directly into your Harness CI pipeline steps at runtime —
no secrets stored in Harness, no plaintext in pipeline configs.
## Documentation
For setup and usage, visit the [GitHub repository](https://github.com/Keeper-Security/harness-integration).
## How to Use This Image
```yaml
step:
type: Plugin
spec:
image: keeper/harness-plugin:latest
settings:
ksm_config: <+secrets.getValue("Keeper_Config_Secret")>
secrets: |
RECORD_UID/field/password > DB_PASSWORD
```
## Support and Feedback
For support or bug reports, file an issue on our [GitHub page](https://github.com/Keeper-Security/harness-integration/issues).
+4507
View File
File diff suppressed because it is too large Load Diff
+1 -1
View File
@@ -44,7 +44,7 @@ const processToken = (rawToken) => {
if (!token.startsWith('US:') && !token.startsWith('{')) {
try {
token = Buffer.from(token, 'base64').toString('utf-8').trim();
} catch (e) {
} catch {
// Not base64, use as-is
core.warning('Base64 decode failed, using raw value');
}