GoogleCloudPlatform / GoogleCloudPlatform/pubsec-declarative-toolkit

hub-env: Ambiguity: determine/rename whether the project-parent-folder requires the name or id - specifies the id but the name is working in the deployment - fixed: was folder name - and fix hardcoded dependsOn

Open
#596 4 comments 0 reactions 1 assignee Claimed by @fmichaelobrien View on GitHub
fortinet Networking
Dominant language
Shell
Stars
36
Forks
26
PR merge metrics
No merged PRs in 30d

Description

Still triaging as part of brining up the hub-env in #466 for #258 after the change in #573
The project comes up under the folder ok but I have yet to go through the remaining "kubectl describe" checks on pending kpt render resources that may need the folder numeric id

```
project-parent-folder: project-parent-folder
```
for example if the format is
```
project-parent-folder: 012345...90
or
project-parent-folder_id: 012345...90
```

the following project deployment was ok with
```
# GCP folder to use as parent to this project, lowercase K8S resource name - this needs the ID
project-parent-folder: services-infrastructure
#project-parent-folder: "176411558066"
```
Screenshot 2023-10-22 at 21 20 39

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.