Specify Workspace name

[adamlc]

I've just started to experiment and it looks like this action uses the folder name as the name of the workspace.

Would it be possible to specify the workspace so it doesn't rely on the folder name? Unless I'm missing something :)

I've also noticed that despite what branch is specified, if a VCS workspace is used, then the remote plan always runs against the main branch and not the branch of the pull request etc

[alfespa17]

Hello @adamlc

It is using the workspace folder as the workspace name as you can see in this part of the code:

terrakube-action-github/src/main.ts

Line 44 in 9fd2356

let workspaceId = await terrakubeClient.getWorkspaceId(organizationId, workspaceFolder)

terrakube-action-github/src/terrakube.ts

Line 55 in 9fd2356

core.debug(`GET ${this.gitHubActionInput.terrakubeEndpoint}/api/v1/organization/${organizationId}/workspace?filter[workspace]=name==${workspaceName}"`)

It has been a long time since I update this action (1.5 years ago), maybe it will need a few adjustments.

[alfespa17]

There is one example that show how to use the action here

[adamlc]

@alfespa17 yes thanks, I can confirm that using the folder name did indeed work. Ideally it would be great if we could just specify a workspace ID, otherwise we'll have to refactor quite a lot of our TF config :)

[alfespa17]

@alfespa17 yes thanks, I can confirm that using the folder name did indeed work. Ideally it would be great if we could just specify a workspace ID, otherwise we'll have to refactor quite a lot of our TF config :)

I dont think this will require a lot of changes basically instead of searching the workspaceId here using the workspaceFolder you could read the workspaceId from the "terrakube.json" that for now only has the terraform version, reading data from that configuration file is quite simple like this

I dont have a lot of bandwith for the following weeks but if you would like to help with this feature all pull request are welcome