You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Within our Azure DevOps environment we feel overwhelmed by having to maintain two completely distinct variable libraries, it would be beneficial to us to identify the commonly shared value between environments and move those into a common library for use between both Prod and Staging. While retaining environment specific values in their respective Prod and Staging variable libraries. In this process we would also need to cleanup any superfluous or redundant variables.
Pre-Conditions:
Functioning variable libraries for Prod and Staging
Acceptance Criteria:
Common library for shared values between staging and prod environments within AzDO
Removal of redundant/superfluous values within Prod and Staging Var libraries
Retention of environment implementation specific values within their respective libraries
Pain Avoided/Frustration Saved:
Managing two distinct variable libraries and having to update them both when changes are made
Breadth/Pervasiveness of Problem:
The entirety of the Azure DevOps deployment workflow
Complexity of Problem (Low, Medium, High) and Why it's Complex:
Complexity is: Medium
Reason why is:
The text was updated successfully, but these errors were encountered:
governmentSponsored
changed the title
DevEx/OpEx Template (Clone this issue to create a new DevEx/OpEx issue)
Azure DevOps Env Var Cleanup and Simplification
Feb 11, 2025
Within our Azure DevOps environment we feel overwhelmed by having to maintain two completely distinct variable libraries, it would be beneficial to us to identify the commonly shared value between environments and move those into a common library for use between both Prod and Staging. While retaining environment specific values in their respective Prod and Staging variable libraries. In this process we would also need to cleanup any superfluous or redundant variables.
Pre-Conditions:
Acceptance Criteria:
Pain Avoided/Frustration Saved:
Breadth/Pervasiveness of Problem:
Complexity of Problem (Low, Medium, High) and Why it's Complex:
Complexity is: Medium
Reason why is:
The text was updated successfully, but these errors were encountered: