Configure a diskette¶
Every diskette loaded on a floor has the Configuration button in the floor's drive. It opens the diskette's configuration: the values it uses to work (accounts, users, keys), which you can change after loading, without reloading the floor. A diskette that uses no values shows a notice that there is nothing to configure.
What you choose when loading (for example, the language of a report) stays in the loading form and does not show up on this screen.
Some diskettes need data only you have, such as your cloud credential. They don't ask for it when you load them: the diskette enters the floor waiting for configuration, and you fill in the configuration afterwards, with a test right away.
How it works¶
- You load the diskette on the floor. Loading asks for no credential at all.
- In the floor's drive, the diskette shows «Waiting for configuration» and the Configure button. Whatever depends on the configuration does not run yet.
- In Configure, you fill in the fields. Only the tower owner can edit; someone with read-only access sees what is set. Before editing, Husvord asks you to sign in again: the sign-in must be less than 5 minutes old.
- When you click Save and test, Husvord tests the configuration right away:
- it works: the diskette becomes Configured and can start working (in the case of an audit, the run becomes available for you to request);
- it fails: the screen shows the reason, in Portuguese, English or Spanish, and you fix it and save again.
Secrets (keys, passwords) go straight to your tower's secret store. They never come back to the screen: you only see when they were set and by whom, and a Replace button. To replace a key or switch the account later, just save again: the test runs again and there is no need to reload the floor. If the test fails during a replacement, the diskette goes back to waiting for configuration until a test passes.
Some values are generated by Husvord and are shown only for you to copy (for example, a connection identifier that comes already filled in the file you download). They cannot be edited.
Example: AWS Audit¶
The AWS Audit asks, in its configuration, for a read-only role and a service user that you create in your account with a template the floor itself hands you. The full step-by-step is in AWS Audit: connect your account.