Establish and standardise environment representative directory structure for storing configuration data for deployments, and deployment mechanisms that use this structure, for AA0.5

Currently, there is no single source of truth for all application configuration at the SKAO.  By building out a secure version controlled repository with easy access, and integration to application deployment it will be possible to separately maintain configuration from  code that enables deployment without maintaining separate or branched versions of code.

Linking the environment configuration by using the standardised directory structure also used in the Gitlab pipeline definitions makes it easy to see at a glance how the deployments to an environment link up to the configuration in those deployments. If there is a seamless correlation between the way configuration data of environments and deployment information for those environments is stored, configuration can be automated using the already standardised CI machinery with a low amount of effort.

• A well defined unified hierarchy is implemented in Vault that supports
  • datacentres
  • environments
  • services
  • developers
• infrastructure and pipeline machinery deployments are migrated to new structure
• changes and migration processes are demonstrated and advertised to teams
• documentation in developer portal is restructured/rewritten to reflect the new configuration solution