The following configuration creates both a project and folder at the org level - not nested
I would expect that the parent of the project be the LZ_FOLDER_NAME (or more accurately LZ_FOLDER_ID)
defaults to org parent - there is no mention of what is "option 2"
gcloud projects create "$PROJECT_ID" --set-as-default --organization="$ORG_ID"
export PROJECT_ID=pdt-arg-kcc3
export LZ_FOLDER_NAME=pdt-arg-kcc3
export ROOT_FOLDER_ID= # This one is only required if not deploying at the org level. Ex. for testing. See option 2 when executing the Config Controller project and cluster below
Assigned fmichaelobrien
The following configuration creates both a project and folder at the org level - not nested I would expect that the parent of the project be the LZ_FOLDER_NAME (or more accurately LZ_FOLDER_ID)
https://github.com/ssc-spc-ccoe-cei/gcp-tools/blob/main/scripts/bootstrap/setup-kcc.sh#L27
defaults to org parent - there is no mention of what is "option 2" gcloud projects create "$PROJECT_ID" --set-as-default --organization="$ORG_ID"