[docs] Changed ENV vars from code to complete list

[micbar]

Description

User Stories

• As a technical stakeholder i want to know all possible changes to my deployments during an upgrade to prevent issues

Value

• Prevention of Issues

Acceptance Criteria

• List of changed ENV vars can be created for every release
  • Variable Name
  • Introduced in version
  • Default Value
  • Description
  • dependencies with user other components

Definition of ready

• Everybody needs to understand the value written in the user story
• Acceptance criteria have to be defined
• All dependencies of the user story need to be identified
• Feature should be seen from an end user perspective
• Story has to be estimated
• Story points need to be less than 20

Definition of done

• Functional requirements
  • Functionality described in the user story works
  • Acceptance criteria are fulfilled
• Quality
  • Code review happened
  • CI is green (that includes new and existing automated tests)
  • Critical code received unit tests by the developer
• Non-functional requirements
  • No sonar cloud issues
• Configuration changes
  • The next branch of the ocis charts is compatible

[micbar]

@dragonchaser @kobergj As discussed in the standup

@mmattel FYI