not a vaporware, but a cloudy stuff, about sending back request from where it come from.
using this project, while expecting the same result as outscale API, might have unforeseen consequences. but you're a free man, so you can try.
if you want Ricochet to Rise and Shine, you need to have the right conf in the right place.
1rst argumnent of ricochet is the configuration path.
Example:
{
// either exist, full, mix or none, none ignore all auth, exist, check if the user exist but don't go futher,
// and full do the full auth, full is buggy. mix check password, but not the V4 signature.
"auth_type": "headarches",
"tls": false, // start the server as an http/https server
"in_convertion": true, // support for FCU/ICU and other non outscale API (just support a very few call so far)
"password_as_ak": true, // password auth, is now consider as strong as ak/sk
"users": [ // Can have multiple users
{
"access_key": "11112211111110000000",
"secret_key": "0000001111112222223333334444445555555666",
"login": "joe",
"pass": "ashita wa dochida"
},
{
"access_key": "11112211111110000333",
"secret_key": "1000001111112222223333334444445555555666",
"login": "titi",
"pass": "toto"
}
]
}
cargo build
cargo run [-- CONFIG.json]
for config see this and that as example
{
"log": {
"scope": ["nets", "vms"],
"dir": "all"
}
}
"scope"
is an array of what resources you want to log, like ["nets", "vms"]
"dir"
is used to set if you want to see input or output arguments, either "in", "out" or "all"
Example:
curl 127.0.0.1:3000/SetLog_ -d '{"log": {"scope": ["nets"], "dir": "in"}}'
[oapi-cli]
|
V
(createVms) -> [ricochet-2]
|
V
(create a VM)
|
V
[oapi-cli] <---- (Send return)
|
V
(Print Result)
------- Some time later with a different client ----
[curl]
|
V
(ReadVms) -> [ricochet-2]
|
V
[curl] <- (Send earlier created VM)
|
V
(print result)
You can open a PR, or an issue