rich-whale-93740
12/16/2025, 6:36 AMparent environment, which imports a few children, e.g. child1, child2, and then define a role to be able to "open" parent, we would need to allow the role to access all children one by one. It becomes trickier when child3 is imported. Sometimes we forget the step to allow the role to access child3 because we just assume having access parent implicitly grants permission to all imported environments
When we use External Secrets Operator to sync parent to the cluster via an access token, we would get a 400 error in such case, which sometime result in long time debugging
Any suggestion?mammoth-restaurant-4670
12/16/2025, 3:10 PMsilly-country-86708
12/16/2025, 4:59 PMrich-whale-93740
12/16/2025, 5:16 PMsilly-country-86708
12/18/2025, 1:04 AM.import * as pulumiservice from "@pulumi/pulumiservice";
const envFamily = ["parent", "child1", "child2", "child3"];
envFamily.forEach(env => {
new pulumiservice.TeamEnvironmentPermission(`perm-${env}`, {
organization: "myorg",
project: "myproject",
environment: env,
team: "backend-team",
permission: pulumiservice.EnvironmentPermission.Open,
});
});