Compare commits

..

2 Commits

Author SHA1 Message Date
b11b974dad chore: Set RUST_LOG to something sensible by default when running with cargo
All checks were successful
Build and deploy / build (push) Successful in 9m30s
Build and deploy / Deploy container (push) Successful in 38s
2025-09-05 03:55:04 +02:00
8c37c994fe feat(config)!: Reworked how configuration is loaded
The environment variable `AUTOMATION_CONFIG` has been renamed to
`AUTOMATION__ENTRYPOINT` and can now also be set in `automation.toml` by
specifying:
```
automation = "<path>"
```

Directly accessing the environment variables in lua in no longer
possible. To pass in configuration or secrets you can now instead make
use of the `variables` and `secrets` modules.

To set values in these modules you can either specify them in
`automation.toml`:
```
[variables]
<name> = <value>

[secrets]
<name> = <value>
```
Note that these values will get converted to a string.

You can also specify the environment variables
`AUTOMATION__VARIABLES__<name>` and `AUTOMATION__SECRETS__<name>` to
set variables and secrets respectively. By adding the suffix `__FILE` to
the environment variable name the contents of a file can be loaded into
the variable or secret.

Note that variables and secrets are identical in functionality and the
name difference exists purely to make it clear that secret values are
meant to be kept secret.
2025-09-05 03:55:04 +02:00

View File

@@ -3,6 +3,8 @@ local utils = require("utils")
local secrets = require("secrets") local secrets = require("secrets")
local debug = require("variables").debug or false local debug = require("variables").debug or false
print(debug)
print(_VERSION) print(_VERSION)
local host = utils.get_hostname() local host = utils.get_hostname()