feat: import/export of config and secrets

[matt2e]

closes #1948

Usage:

Exporting
Prints json of all secrets to stdout:
ftl secret export

Exports all inline secrets to a json file
ftl secret export --inline > exported.json

Importing
Imports json from a file:
ftl secret import --inline exported.json

Migrating
Migrates inline secrets to 1Password:
ftl secret export --inline | ftl secret import --op --opvault <vauld id>

JSON Format

{
    "<module>.<name>": <secret>,
    ...
}

[alecthomas]

Why the change? The previous function was generalisable to any Action.

[matt2e]

I went in circles a bit on this:

• When I used ExecWithOutput I expected to be able to use the output. It didn't indicate that it was only capturing the output in case of an error
• I then tried to make ExecWithOutput work for both success success and error cases:
  • For success cases, call a func with the output (like the replacement ExecWithOutput action I added)
  • For error cases throw the error with the output (old behaviour)
• It then felt a bit messy for the error case so I tried cleaning it up.

I can go back to ExecWithOutput handling both cases. Thoughts?

[alecthomas]

I think it's fine to introduce new functionality, but that doesn't seem like a reason to remove in.ExpectError()?

[matt2e]

Yeh I see what you mean. I've moved them back into one func called ExecWithOutput which works like before for the error case (used in conjunction with ExpectError and an empty capture func).

[alecthomas]

What's the behaviour when restoring, I assume it will just write the values in the dump, not remove any extra keys in the target?

[alecthomas]

FYI @AlexSzlavik

[matt2e]

What's the behaviour when restoring, I assume it will just write the values in the dump, not remove any extra keys in the target?

That's right. Existing refs that aren't in the dump aren't touched. So it's less of a "restore" and more of an "import"