No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

```argocd@argo-cd-argocd-repo-server-55d7cdfb97-xtkp7:/tmp/_argocd-repo/52c01366-05dc-4758-9681-a63572526b17/infra$ stat $(pwd)
  File: /tmp/_argocd-repo/52c01366-05dc-4758-9681-a63572526b17/infra
  Size: 193       	Blocks: 0          IO Block: 4096   directory
Device: 10301h/66305d	Inode: 75495274    Links: 9
Access: (0755/drwxr-xr-x)  Uid: (  999/  argocd)   Gid: (  999/  argocd)
Access: 2023-03-23 03:44:11.481492993 +0000
Modify: 2023-03-23 03:44:11.517493089 +0000
Change: 2023-03-23 03:44:11.517493089 +0000
 Birth: 2023-03-23 03:44:11.481492993 +0000```


Perhaps this is some weird implicit behavior of some common lib/function/etc, but it just smells wrong.

```argocd@argo-cd-argocd-repo-server-55d7cdfb97-xtkp7:/tmp/_argocd-repo/52c01366-05dc-4758-9681-a63572526b17/infra$ pulumi whoami
error: failed to locate Pulumi.yaml project file: open /tmp/_argocd-repo/52c01366-05dc-4758-9681-a63572526b17/infra: permission denied```

it seems to be invoked by the whoami logic, and I see this stuff was recently changed in recent merges

```argocd@argo-cd-argocd-repo-server-55d7cdfb97-xtkp7:/tmp/_argocd-repo/52c01366-05dc-4758-9681-a63572526b17/infra$ pulumi login file:///tmp/tmp.Wqvf7DFQPz
error: failed to locate Pulumi.yaml project file: open /tmp/_argocd-repo/52c01366-05dc-4758-9681-a63572526b17/infra: permission denied
argocd@argo-cd-argocd-repo-server-55d7cdfb97-xtkp7:/tmp/_argocd-repo/52c01366-05dc-4758-9681-a63572526b17/infra$ echo $?
255```

I think I pinpointed the actual exit code

<https://github.com/pulumi/pulumi/issues/12481>

I opened/reported this - I know it's a strange edgecase, but it is one indeed.

I can reliably reproduce it just by creating a directory structure that removes read from the root-parent.

Also if anyone else runs into this, I was able to workaround it by doing
```		cd $HOME
		${PULUMI_CMD} login file://$pulumi_state_temp
		cd -```


It appears that pulumi update works just fine - it is just login that barfs on the permission problem