Files
opencloud/docs/ocis/development/deprecating-variables.md
T
Christian Richter 28c6d1dbfa Add dev-docs for variable descrption
Signed-off-by: Christian Richter <crichter@owncloud.com>
2022-11-29 16:02:33 +01:00

1.5 KiB

title, date, geekdocRepo, geekdocEditPath, geekdocFilePath
title date geekdocRepo geekdocEditPath geekdocFilePath
Deprecating Variables 2022-11-29T15:41:00+01:00 https://github.com/owncloud/ocis edit/master/docs/ocis/development deprecating-variables.md

{{< toc >}}

Deprecating Environment Variables

Sometimes it is necessary to deprecate environment to align their naming with conventions. We therefore added annotations to automate the documentation process. It is necessary to know when the variable is going to be deprecated, when it is going to be removed and why.

Example

// Nats is the nats config
type Nats struct {
Host string `yaml:"host" env:"NATS_HOST_ADDRESS,NATS_NATS_HOST" desc:"Bind address." deprecationVersion:"1.6.2" removalVersion:"1.7.5" deprecationInfo:"NATS_NATS_HOST is confusing" deprecationReplacement:"NATS_HOST_ADDRESS"`
...
}

There are four different annotation variables that need to be filled:

Annotation Description Format
depreactionVersion The version the variable will be deprecated semver (e.g. 1.6.2)
removalVersion The version the variable will be removed from the codebase semver (e.g. 1.7.3)
deprecationInfo Information why the variable is deprecated, must start with the name of the variable in order to avoid confusion, when there are multiple options in the env:-field string (e.g. NATS_NATS_HOST is confusing)
depreactionReplacement The name of the variable that is going to replace the deprecated on. string (e.g. NATS_HOST_ADDRESS)