
Security News
vlt Launches "reproduce": A New Tool Challenging the Limits of Package Provenance
vlt's new "reproduce" tool verifies npm packages against their source code, outperforming traditional provenance adoption in the JavaScript ecosystem.
@harnessio/backstage-plugin-ci-cd
Advanced tools
Welcome to the Harness NextGen CI/CD plugin for Backstage!
# From your Backstage root directory
yarn add --cwd packages/app @harnessio/backstage-plugin-ci-cd
yarn install
app-config.yaml
under proxy config. Add your Harness Personal Access Token or Service Account Token for x-api-key
(see the Harness docs )# In app-config.yaml
proxy:
# ...
'/harness':
target: 'https://app.harness.io/'
headers:
'x-api-key': '<YOUR PAT/SAT>'
# ...
Note: Plugin uses token configured here to make Harness API calls. Make sure this token has the necessary permissions.
EntityPage.tsx
, update the cicdContent
to render <EntityHarnessCiCdContent />
whenever service is using Harness CI/CD. Example below// In packages/app/src/components/catalog/EntityPage.tsx
import {
isHarnessCiCdAvailable,
EntityHarnessCiCdContent
} from '@harnessio/backstage-plugin-ci-cd';
const cicdContent = (
// ...
<EntitySwitch.Case if={isHarnessCiCdAvailable}>
<EntityHarnessCiCdContent />
</EntitySwitch.Case>
// ...
);
Note: If you have separate providers for CI and CD apart from Harness, you need to add a new tab for Harness CI/CD plugin like below instead of replacing your existing CI/CD tab mentioned in above block.
// In packages/app/src/components/catalog/EntityPage.tsx
import {
isHarnessCiCdAvailable,
EntityHarnessCiCdContent
} from '@harnessio/backstage-plugin-ci-cd';
const serviceEntityPage = (
// ...
<EntityLayout.Route path="/harness-ci-cd" title="Harness CI/CD" if={isHarnessCiCdAvailable}>
<EntityHarnessCiCdContent />
</EntityLayout.Route>
// ...
);
app-config.yaml
# In app-config.yaml
harness:
baseUrl: https://app.harness.io/
apiVersion: backstage.io/v1alpha1
kind: Component
metadata:
# ...
annotations:
# mandatory annotations
harness.io/project-url: <harness_project_url>
# optional annotations
harness.io/ci-pipelineIds: <pipelineId1,pipelineId2,pipelineId3 etc>
harness.io/cd-serviceId: <serviceId>
spec:
type: service
# ...
Note: Refer to this page on how to get these values from your Harness account.
FAQs
Website: [https://harness.io/](https://harness.io/)
The npm package @harnessio/backstage-plugin-ci-cd receives a total of 907 weekly downloads. As such, @harnessio/backstage-plugin-ci-cd popularity was classified as not popular.
We found that @harnessio/backstage-plugin-ci-cd demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
vlt's new "reproduce" tool verifies npm packages against their source code, outperforming traditional provenance adoption in the JavaScript ecosystem.
Research
Security News
Socket researchers uncovered a malicious PyPI package exploiting Deezer’s API to enable coordinated music piracy through API abuse and C2 server control.
Research
The Socket Research Team discovered a malicious npm package, '@ton-wallet/create', stealing cryptocurrency wallet keys from developers and users in the TON ecosystem.