This message was deleted.

If you leave out the

folderId

the project will be created as a personal project, which you can always do (almost). Do you have the Project Creator role across the whole organization?

Yes. The project is created underneath the organization without the folderId. But I want it to be underneath the folder. From docs side it looks like setting the arg and be fine with it 🤷‍♂️

You can use

folder.name

: https://www.pulumi.com/docs/reference/pkg/gcp/organizations/folder/#outputs

makes no difference - error still the same

Here we just give the

folder_id

as in the api on the config file. The

id

output might not be it exactly, since the provider can change to add some prefix, and the

name

output is

folder/{folder_id}

, which is what is used to create a nested folder, but not a project.

Nested Folder works. The folder -> project nesting results in „already exists“. But there is no such project. That’s why I assume no permission failure

You might be reusing a project id. Have you created a "some-id" project in the past and deleted it? In that case, you will need a new id.

My issue was changing from an organization level project to a project underneath a folder. This did not work due to an error „cannot set both org_id and folder_id“. By creating a new folder and a new project from scratch I was able to build the structure.