You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A configuration file, to be stored as a json file and contains important variables/flags that hack/quickstart-setup.sh detects and runs the script without prompts .
How:
The configuration file could look like:
{
"key": "value",
"key1": "value1"
}
And can include important details such as running in single cluster or multi cluster mode, which DNS Provider (if any) wants to be used, followed by DNS Provider specific env vars, etc.
The script can check for a filename (maybe conf.json) within a set location, such as hack/, or the script can check for a passed in/set variable (maybe KUADRANT_CONF=<file>.json). When it detects that file, it can read in the variables from quiet mode mentioned in #743 so that both modes offer equivalent functionality .
This issue will need to be followed up by a docs write up explaining the new changes .
The text was updated successfully, but these errors were encountered:
It wouldn't replace the env vars, rather add more flexibility to our set up already. Take a look at the comments made by myself and @Boomatang here --> #744 (comment) . Let me know if you have other concerns about this.
What:
A configuration file, to be stored as a
json
file and contains important variables/flags thathack/quickstart-setup.sh
detects and runs the script without prompts .How:
The configuration file could look like:
And can include important details such as running in single cluster or multi cluster mode, which DNS Provider (if any) wants to be used, followed by DNS Provider specific env vars, etc.
The script can check for a filename (maybe
conf.json
) within a set location, such ashack/
, or the script can check for a passed in/set variable (maybeKUADRANT_CONF=<file>.json
). When it detects that file, it can read in the variables from quiet mode mentioned in #743 so that both modes offer equivalent functionality .This issue will need to be followed up by a docs write up explaining the new changes .
The text was updated successfully, but these errors were encountered: