docs: Promote user-info-fetcher docs to navgation

[sbernauer]

Description

Given that we are using it extensively already (e.g. in the e2e-security demo) and me handing out the link to multiple customers, I would like to promote https://docs.stackable.tech/home/nightly/opa/usage-guide/user-info-fetcher.html to include it in the navigation

Definition of Done Checklist

• Not all of these items are applicable to all PRs, the author should update this template to only leave the boxes in that are relevant
• Please make sure all these things are done and tick the boxes

# Author
- [ ] Changes are OpenShift compatible
- [ ] CRD changes approved
- [ ] CRD documentation for all fields, following the [style guide](https://docs.stackable.tech/home/nightly/contributor/docs-style-guide).
- [ ] Helm chart can be installed and deployed operator works
- [ ] Integration tests passed (for non trivial changes)
- [ ] Changes need to be "offline" compatible

# Reviewer
- [ ] Code contains useful comments
- [ ] Code contains useful logging statements
- [ ] (Integration-)Test cases added
- [ ] Documentation added or updated. Follows the [style guide](https://docs.stackable.tech/home/nightly/contributor/docs-style-guide).
- [ ] Changelog updated
- [ ] Cargo.toml only contains references to git tags (not specific commits or branches)

# Acceptance
- [ ] Feature Tracker has been updated
- [ ] Proper release label has been added
- [ ] [Roadmap](https://github.com/orgs/stackabletech/projects/25/views/1) has been updated

[Maleware]

LGTM! Thank you :)

[sbernauer]

Giving @nightkr and @NickLarsenNZ a chance to comment...

[nightkr]

Have we addressed the client API side yet? We shouldn't have been shipping it to demos or customers before that, and the linked docs definitely don't.

[sbernauer]

Are you talking about the API described in https://docs.stackable.tech/home/nightly/opa/usage-guide/user-info-fetcher.html#_user_info_fetcher_api?
Currently you can send an username or id and get all infos we can collect back. What exactly do you want to address, would you like to change the API?

[nightkr]

The UIF provides the HTTP API, but we should wrap that in an OPA rule we provide (and can update), rather than have everyone hard-code the HTTP stuff themselves.

[fhennig]

I don't think we have that yet. I agree that it would be good to have. Could we simply have a uif rego package that we deploy when the UIF is enabled? and users can import the package in their own code?

I think we can still do this 'promotion' here and do a follow-up PR to adress this. it's all in nightly anyways, but we need to prioritise the follow-up then

edit: I made a ticket for this: #558

[sbernauer]

Yeah, I can see the point of providing a regorule in addition to the HTTP API. The question is if we should block the docs on the API until the rego rules are there 🤔

[nightkr]

I don't think we have that yet. I agree that it would be good to have. Could we simply have a uif rego package that we deploy when the UIF is enabled? and users can import the package in their own code?

Yes, basically this.

I think we can still do this 'promotion' here and do a follow-up PR to adress this. it's all in nightly anyways, but we need to prioritise the follow-up then.

I'd rather avoid keeping main in an unreleasable state.. but especially when even temporary nightly changes end up on https://docs.stackable.tech/home/nightly/index.html immediately (almost) and cause more confusion.

Yeah, I can see the point of providing a regorule in addition to the HTTP API. The question is if we should block the docs on the API until the rego rules are there 🤔

We should, because the current HTTP API is not public or stable. The uif package is the stable API surface, the HTTP API is just an implementation detail for how to get there.

[fhennig]

Okay I agree with @nightkr, so maybe we can put #558 on the board either to be refined or ready for development, and then block this PR on the other ticket? Or we shelf the whole thing for now. paging @lfrancke

[fhennig]

blocked by #558

[sbernauer]

I think the change is trivial and I would close this PR until everyone thinks we are ready to include the docs in the navigation

[sbernauer]

Reopening according to the decision in the daily, as we where not able to ship #558 in time for the 23.07 release

[NickLarsenNZ]

LGTM

[Techassi]

Some suggestions.

Outdated