4f317b8499
Validate the Kamal configuration giving useful warning on errors. Each section of the configuration has its own config class and a YAML file containing documented example configuration. You can run `kamal docs` to see the example configuration, and `kamal docs <section>` to see the example configuration for a specific section. The validation matches the configuration to the example configuration checking that there are no unknown keys and that the values are of matching types. Where there is more complex validation - e.g for envs and servers, we have custom validators that implement those rules. Additonally the configuration examples are used to generate the configuration documentation in the kamal-site repo. You generate them by running: ``` bundle exec bin/docs <kamal-site-checkout> ```
37 lines
1.0 KiB
Ruby
37 lines
1.0 KiB
Ruby
class Kamal::Configuration::Env
|
|
include Kamal::Configuration::Validation
|
|
|
|
attr_reader :secrets_keys, :clear, :secrets_file, :context
|
|
delegate :argumentize, to: Kamal::Utils
|
|
|
|
def initialize(config:, secrets_file: nil, context: "env")
|
|
@clear = config.fetch("clear", config.key?("secret") || config.key?("tags") ? {} : config)
|
|
@secrets_keys = config.fetch("secret", [])
|
|
@secrets_file = secrets_file
|
|
@context = context
|
|
validate! config, context: context, with: Kamal::Configuration::Validator::Env
|
|
end
|
|
|
|
def args
|
|
[ "--env-file", secrets_file, *argumentize("--env", clear) ]
|
|
end
|
|
|
|
def secrets_io
|
|
StringIO.new(Kamal::EnvFile.new(secrets).to_s)
|
|
end
|
|
|
|
def secrets
|
|
@secrets ||= secrets_keys.to_h { |key| [ key, ENV.fetch(key) ] }
|
|
end
|
|
|
|
def secrets_directory
|
|
File.dirname(secrets_file)
|
|
end
|
|
|
|
def merge(other)
|
|
self.class.new \
|
|
config: { "clear" => clear.merge(other.clear), "secret" => secrets_keys | other.secrets_keys },
|
|
secrets_file: secrets_file || other.secrets_file
|
|
end
|
|
end
|