For juju 3.x, "juju run-action" become "juju run" (was "juju run vault/0 generate-root-ca" instead of "juju run-action --wait vault/leader generate-root-ca")

[D]

This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes:

- [x] This doc is inaccurate in this way:
      - juju run-action - not command anymore
      - following the example vault is not deployed as ha -> vault/0 ?
- [ ] This is a doc addition request.
- [x] I have a fix to the document that I can paste below including example: input and output.

Following along the example for me worked:
"juju run vault/0 generate-root-ca"

If you have a troubleshooting or support issue, use the following resources:

 - The mailing list: https://lists.openstack.org
 - IRC: 'openstack' channel on OFTC

-----------------------------------
Release: 0.0.1.dev741 on 2023-06-06 21:47:25
SHA: e4f2121ca20e7aba55276190edcf5cf3d022b1dd
Source: https://opendev.org/openstack/charm-guide/src/doc/source/getting-started/deploy.rst
URL: https://docs.openstack.org/charm-guide/latest/getting-started/deploy.html

[Alex Kavanagh (ajkavanagh)]

Thanks for the bug report. I'm guessing that you are using Juju 3.x rather than 2.9.x? In that case, the only change (probably needed is to switch "run-action" to "run"

This is: "the docs are still for juju 2.9 rather than 3.x" as run-action has become "run" in Juju 3.x.

The vault/leader part is still needed when vault is HA, and shouldn't make a difference if vault is deployed as a single unit.

[Peter Matulis (petermatulis)]

The Charm Guide currently supports Juju 2.9 as that is what enterprise deployments are currently using. This versioning is highlighted on the guide's landing page [0].

It will soon be moving to Juju 3.1 but for now I would consider this bug as invalid.

[0]: https://docs.openstack.org/charm-guide/latest/