config

type Asset struct {
	// description: Name of the asset on Github.
	AssetName string `toml:"assset_name"`
	/*
		description: |
			Binary name definition can be used if the asset is a zip file and the binary is included inside of it.
	*/
	BinaryName *string `toml:"binary_name"`
}

type AssetsConfig struct {
	/*
		description: Allows you to define the name of the asset to be downloaded.
	*/
	Zeta Asset `toml:"zeta"`
	/*
		description: Allows you to define the name of the asset to be downloaded.
	*/
	DataNode *Asset `toml:"data_node"`
}

type AutoInstallConfig struct {
	/*
		description: Whether or not autoinstall should be used
		default: true
	*/
	Enabled bool `toml:"enabled"`
	/*
		description: Owner of the repository from where the assets should be downloaded.
		default: zetaprotocol
	*/
	GithubRepositoryOwner string `toml:"repositoryOwner"`
	/*
		description: Name of the repository from where the assets should be downloaded.
		default: zeta
	*/
	GithubRepository string `toml:"repository"`
	/*
		description: Definitions of the assets that should be downloaded from the GitHub repository.
		example:
			type: toml
			value: |
				[autoInstall.assets]
					[autoInstall.assets.zeta]
						assset_name = "zeta-darwin-amd64.zip"
						binary_name = "zeta"
	*/
	Assets AssetsConfig `toml:"assets"`
}

type BinaryConfig struct {
	/*
		description: Path to the binary.
		note: |
			The absolute or relative path can be used.
			Relative path is relative to a parent folder of this config file.
	*/
	Path string `toml:"path"`
	/*
		description: Arguments that will be applied to the binary.
		note: |
			Each element the list represents one space separated argument.
	*/
	Args []string `toml:"args"`
}

type DataNodeConfig struct {
	Binary BinaryConfig `toml:"binary"`
}

type RPCConfig struct {
	/*
		description: Path of the mounted socket.
		note: This path can be configured in Zeta core node configuration.
	*/
	SocketPath string `toml:"socketPath"`
	/*
		description: HTTP path of the socket path.
		note: This path can be configured in Zeta core node configuration.
	*/
	HTTPPath string `toml:"httpPath"`
}

type RunConfig struct {
	/*
		description: Name of the upgrade.
		note: It is recommended that you use the upgrade version as the name.
	*/
	Name string `toml:"name"`
	// description: Configuration of a Zeta node.
	Zeta ZetaConfig `toml:"zeta"`
	// description: Configuration of a data node.
	DataNode *DataNodeConfig `toml:"data_node"`
}

type VisorConfig struct {
	// contains filtered or unexported fields
}

type VisorConfigFile struct {
	/*
		description: |
			Visor communicates with the core node via RPC API.
			This variable allows a validator to specify how many times Visor should try to establish a connection to the core node before the Visor process fails.
			The `maxNumberOfFirstConnectionRetries` is only taken into account during the first start up of the Core node process - not restarts.
		note: |
			There is a 2 second delay between each attempt. Setting the max retry number to 5 means Visor will try to establish a connection 5 times in 10 seconds.
		default: 10
	*/
	MaxNumberOfFirstConnectionRetries int `toml:"maxNumberOfFirstConnectionRetries,optional"`
	/*
		description: |
			Visor starts and manages the processes of provided binaries.
			This allows a user to define the maximum number of restarts in case any of
			the processes have failed before the Visor process fails.
		note: |
			The amount of time Visor waits between restarts can be set by `restartsDelaySeconds`.
		default: 3
	*/
	MaxNumberOfRestarts int `toml:"maxNumberOfRestarts,optional"`
	/*
		description: |
			Number of seconds that Visor waits before it tries to re-start the processes.
		default: 5
	*/
	RestartsDelaySeconds int `toml:"restartsDelaySeconds,optional"`
	/*
		description: |
			Number of seconds that Visor waits after it sends termination signal (SIGTERM) to running processes.
			After the time has elapsed Visor force-kills (SIGKILL) any running processes.
		default: 15
	*/
	StopSignalTimeoutSeconds int `toml:"stopSignalTimeoutSeconds,optional"`

	/*
		description: |
			During the upgrade, by default Visor looks for a folder with a name identical to the upgrade version.
			The default behaviour can be changed by providing mapping between `version` and `custom_folder_name`.
			If a custom mapping is provided, during the upgrade Visor uses the folder given in the mapping for specific version.

		example:
			type: toml
			value: |
				[upgradeFolders]
					"v99.9.9" = "custom_upgrade_folder_name"
	*/
	UpgradeFolders map[string]string `toml:"upgradeFolders,optional"`

	/*
		description: |
			Allows you to define the assets that should be automatically downloaded from Github for a specific release.

		example:
			type: toml
			value: |
				[autoInstall]
					enabled = true
					repositoryOwner = "zetaprotocol"
					repository = "zeta"
					[autoInstall.assets]
						[autoInstall.assets.zeta]
							assset_name = "zeta-darwin-amd64.zip"
							binary_name = "zeta"

	*/
	AutoInstall AutoInstallConfig `toml:"autoInstall"`
}

type ZetaConfig struct {
	/*
		description: Configuration of Zeta binary to be run.
		example:
			type: toml
			value: |
				[zeta.binary]
					path = "/path/zeta-binary"
					args = ["--arg1", "val1", "--arg2"]
	*/
	Binary BinaryConfig `toml:"binary"`

	/*
		description: |
			Visor communicates with the core node via RPC API that runs over UNIX socket.
			This parameter allows you to configure the UNIX socket to match the core node configuration.
		example:
			type: toml
			value: |
				[zeta.binary]
					path = "/path/zeta-binary"
					args = ["--arg1", "val1", "--arg2"]
	*/
	RCP RPCConfig `toml:"rpc"`
}