tests/vault/client content written with Claude Sonnet 4 assistance.

In T2124#32520, @dereckson wrote:

Next steps for full automation:

• allow to login with proper credentials
  • Vault via rOPS: Create a permission for access to relevant credentials (see first comment of this post, acquisitariat not needed)
  • Vault manually: Create an AppRole linked to that permission
  • Code: allow to login to Vault with AppRole when available in environment or when a file exists, TO IMPLEMENT FOR BOTH TOOLS (bot needs Agora, run-report needs db-B-001).
• deploy the bot on WindRiver
  • Vault via rOPS: credentials to query Vault (ie secret id and role id from the AppRole)
  • Salt: create rhyne-wyse user
  • Salt: create /var/db/rhyne-wyse, chown to rhyne-wyse:nasquenautes in 775, so everyone can run the bot too
  • Salt: provide /etc/periodic configuration to run the script daily

Tested correctly with Complector and WindRiver. Can run the bot succesfully afterwards.

Just for information, log doesn't have any timestamp.

Proper headers for Sphinx autogenerated configuration

No need to build secretsmith in rOPS, going to push to PyPI once doc is published at https://docs.nasqueron.org/secretsmith

Rebased. Rhyne-Wise -> Rhyne-Wyse too here.

Mail sent 2025-09-20.

Improve package installation and detection. A module is required with cumbersome Python invoke and discovery logic, because Salt can internally report about /opt/saltstack Python installation on Linux OSes, not about the global system default interpreter.

Actually, if we use pip to install the package globally for all users, it will take care creating /usr/local/bin/<utilities> following this entry in setup.cfg:

Merged D3469 so we can have secrets.

Set chmod 755 for the scripts. Rebased against main

AI use

Cleanup README

Packaging. Rebased.