Content Alignment Followup

[ale8k]

Content alignment checks done so far:

• JIMM is a single pane into infrastructure (already there)
• Identity based access control to juju models/controllers
• Transparently proxies Juju clients to models (haven't added this as upcoming work will change it)
• Abstraction of Juju resources irrespective of cloud provider or Juju controller (clear already)
• Single identity, backed by SSO, that works irrespective of which cloud/controller a model lives on (clear already)
• Focal point for Juju ops automation (clear already)
• SREs, I think this is clear by its usage case
• Developers, I think this is clears too no need for more docs on this
• CI/CD/Automation - I don't think we need additional docs for this, it's kinda obvious
• Providing users access to models by identity and not local credentials - Already clear in our security_scope section (rebac part I think makes it clear, but it does still say candid and needs changing later)
• Agreed, switching between Jimmctl and Juju is confusing.
  Non-public charms make deployment difficult. Obtaining dependencies (binaries, charms, snaps, etc.) is hard. - I can't do anything about this really...

[kian99]

lgtm, just a question on one of the points in the description

Transparently proxies Juju clients to models (haven't added this as upcoming work will change it)

What upcoming work is going to change this?

[kian99]

I recommend we get this reviewed by more people, as I'm not sure myself on the finer details of the content-alignment .