Need to automatically accept the warning when setting a secret in GitHub actions using the superfly/flyctl-actions@1.1

[ignoramous]

@aaacafe

can you let me know of any potential pitfalls related to pointing the --config flag to another toml file?

No complications that I can think of. It works nicely for one of the apps I deploy (deploy it twice, once each for the two different fly.tomls; ref).

@aaacafe

i found another way to get this working

A simpler way to get this particular issue is to avoid defining app in fly.toml altogether.