Noah Stride

> We also discussed having this as an experimental feature first. It would be good to point that out in the documents. Yeah - do you think perhaps a header...

I have added "experimental" warning headers to the top of the documents as suggested by @sorindumitru in [0246727](https://github.com/spiffe/spiffe/pull/327/commits/0246727410ff21ad512d67ba257643fb64f01476) - let me know if any of the verbiage needs adjusting.

I see we had https://github.com/spiffe/spiffe/pull/294 for raising PRs for proposals instead - more than happy to raise this as PR. Might make addressing feedback a little easier.

> Forgot to add- speaking for myself and not unilaterally as SSC, I would definitely support similar work for interacting with GCP, Azure, OCI, etc. Definitely agreed - I think...

> but maybe elaborate a bit on whether this is primarily enterprises or smaller organizations as well. For the most part, it feels like accessing AWS from non-AWS hosted workloads...

I'll raise a new issue with those elements addressed next week - apologies - had a busy month with conferences and such but my schedule is looking clearer now!

See https://github.com/spiffe/spiffe/issues/307 for the replacement GitHub issue - feel free to close this one out :)

Sweet idea. Should be pretty easy to do.

Spoke to @hugoShaka and it looks like that endpoint is going to disappear in the mid-term future - we should wait for https://github.com/gravitational/teleport/pull/47126 and then proceed with this task based...

I'm a little worried that pulling the content out of the `workload-identity` directory could make matters more confusing - the content in this directory is all related to a specific...