feat: Add PROJECT_NAME env var to custom workflow hook

[philchristensen]

what

I'd like to be able to use $PROJECT_NAME in the post_workflow_hooks (and pre_workflow_hooks) configuration section. It's already available to run on custom workflows.

why

I'd like to label the PR with info about which TF project was applied.

tests

I updated the tests for these two hooks to test PROJECT_NAME, but I'm still seeing two test errors that seem unrelated in:

--- FAIL: TestRenderProjectResults (0.00s)
    logger.go:146: 2024-08-02T14:38:41.327-0400	INFO	log
    --- FAIL: TestRenderProjectResults/single_successful_policy_check_with_project_name (0.00s)
        --- FAIL: TestRenderProjectResults/single_successful_policy_check_with_project_name/single_successful_policy_check_with_project_name (0.00s)
            markdown_renderer_test.go:1192: [Ran Policy Check for project: `projectname` dir: `path` workspace: `workspace`
            ...
            ...
        --- FAIL: TestRenderProjectResults/single_successful_policy_check_with_project_name/single_successful_policy_check_with_project_name#01 (0.00s)
            markdown_renderer_test.go:1189: [Ran Policy Check for project: `projectname` dir: `path` workspace: `workspace`
            ...
            ...

If I should fix these too, I just need someone who can point in the right direction.

references

• [PROPOSAL] Expose project name as environmental variable in run steps #539
• Add PROJECT_NAME env var to custom run step #578

[X-Guardian]

@philchristensen, the pre/post workflow hooks can have a one to many relationship with projects, so I don't see how this can work.

[philchristensen]

ah, yeah. I wouldn’t mind seeing this as a comma separated list of values. but i can close this for now until i can figure that out…