`firebase deploy` without firebase.json

We have a project that generates four different artifact-websites, each of these has to be deployed to a different Firebase project. We could generate a separate firebase.json file for each but I don’t think it makes much sense. firebase.json is used to generate an archive that’s pushed to Firebase. Why not let us provide everything that’s configurable in JSON file via parameters to firebase deploy? This approach plays really well with CI and fully automated deployments of multiple projects at once.

Here’s an example - this firebase deploy call is equivalent to having a JSON file.

firebase deploy \
  --firebase project-name \
  --public ./build
  --ignore firebase.json \
  --ignore '**/.*'
  --ignore '**/node_modules/**'
  --token abcd

{
  "firebase": "project-name",
  "public": "./build",
  "ignore": [
    "firebase.json",
    "**/.*",
    "**/node_modules/**"
  ]
}

[eirikb]

For my own personal sake I only need --public, and nothing else. - I only want to get rid of a file I actually don’t need.

However, if I had to specify a lot of configuration, but for different environments, I would prefer specifying the name of a configuration file, .e.g, --config firebase-dev.json.
Or perhaps --config dev, and dev is a property under {"firebase": { "dev": { ... } } in package.json.

[mbleigh]

It’s going to be extremely difficult to enumerate the entire array of possible config as command-line options. I’d be more amenable to being able to pass the config JSON inline:

firebase deploy --config '{"hosting":{"public":"dist"}}'

WDYT?