Load account from env var

[amirmalka]

Instead of loading the account from a config map, we will load it from an env var, since account has been moved to a secret. Not applying the same approach as other components since when importing the github.com/kubescape/backend package we have dependencies issues

[codiumai-pr-agent[bot]]

PR Analysis

• 🎯 Main theme: Loading account ID from environment variable

• 📝 PR summary: This PR modifies the main.go file to load the account ID from an environment variable instead of from the cluster data. This change allows for more flexibility and control over the account ID, as it can now be easily changed by modifying the environment variable.

• 📌 Type of PR: Refactoring

• 🧪 Relevant tests added: No

• ⏱️ Estimated effort to review [1-5]: 1, because the PR is small and straightforward, involving only a change in the source of the account ID.

• 🔒 Security concerns: No

  PR Feedback

• 💡 General suggestions: The PR is straightforward and the changes are clear. However, it would be beneficial to include error handling for the case where the environment variable "ACCOUNT_ID" is not set. This would prevent potential issues at runtime.

• 🤖 Code feedback:

  • relevant file: main.go suggestion: Add error handling for the case where the environment variable "ACCOUNT_ID" is not set. This can be done by checking the second return value of os.Getenv("ACCOUNT_ID") and logging an error if it is false. [important] relevant line: os.Getenv("ACCOUNT_ID"),

How to use

To invoke the PR-Agent, add a comment using one of the following commands: /review [-i]: Request a review of your Pull Request. For an incremental review, which only considers changes since the last review, include the '-i' option. /describe: Modify the PR title and description based on the contents of the PR. /improve [--extended]: Suggest improvements to the code in the PR. Extended mode employs several calls, and provides a more thorough feedback. /ask \<QUESTION>: Pose a question about the PR. /update_changelog: Update the changelog based on the PR's contents.

To edit any configuration parameter from configuration.toml, add --config_path=new_value For example: /review --pr_reviewer.extra_instructions="focus on the file: ..." To list the possible configuration parameters, use the /config command.

[github-actions[bot]]

Summary:

• License scan: success
• Credentials scan: success
• Vulnerabilities scan: failure
• Unit test: success
• Go linting: success