From 0bca036143c1ed6cd650d2f51ef57445222736d7 Mon Sep 17 00:00:00 2001 From: Davy McAleer Date: Mon, 30 Mar 2026 15:04:46 +0100 Subject: [PATCH] Update secret names in README for consistency Making the ACCOUNT/SUB_ACCOUNT naming variables the same across both examples and in the description and examples... --- README.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 2ef2cf96..f8dad0a7 100644 --- a/README.md +++ b/README.md @@ -8,7 +8,7 @@ This repository contains a GitHub Action for using FortiCNAPP's code security of ### Creating secrets -Before attempting to run this action, you should add three secrets `LW_ACCOUNT_NAME`, `LW_SUBACCOUNT_NAME` (When using a subaccount) `LW_API_KEY` and `LW_API_SECRET` to your GitHub repository (or, better yet, your GitHub organization so they can be shared across all your repositories). The value for these secrets can be obtained by following the instructions [here](https://docs.lacework.com/console/api-access-keys) to create an API key and then download it. +Before attempting to run this action, you should add three secrets `LW_ACCOUNT`, `LW_SUBACCOUNT` (When using a subaccount) `LW_API_KEY` and `LW_API_SECRET` to your GitHub repository (or, better yet, your GitHub organization so they can be shared across all your repositories). The value for these secrets can be obtained by following the instructions [here](https://docs.lacework.com/console/api-access-keys) to create an API key and then download it. ### Running on pull requests @@ -77,7 +77,8 @@ on: workflow_dispatch: env: - LW_ACCOUNT_NAME: ${{ secrets.LW_ACCOUNT_NAME }} + LW_ACCOUNT_NAME: ${{ secrets.LW_ACCOUNT }} + LW_SUBACCOUNT: ${{ secrets.LW_SUBACCOUNT }} LW_API_KEY: ${{ secrets.LW_API_KEY }} LW_API_SECRET: ${{ secrets.LW_API_SECRET }}