Variables in git
pending feedback
N
Novel Cod
Currently most everything a pipeline reference can be stored in a git except 2 things.
Variables and Overrides V2.
I see there is already an RFE for overrides v2 to be backended by git.
RFE to allow variables to be stored in git.
Now that services are allowed to be stored in git, the variables associated with service are in git. Would request to keep this user experience across the board where variables are first class git citizens
Log In
Pritesh Chandaliya
updated the status to
pending feedback
Pritesh Chandaliya
override v2 is already supported. Docs can be found here: https://developer.harness.io/docs/platform/git-experience/git-settings/#enforce-git-experience
Is the support for variables still a requirement?
Thanks!
A
Abhishek Thamman
updated the status to
open
Autopilot
Merged in a post:
FR - Environment and Infra definition service variables override via git
R
Representative Llama
The requirement here is the ability to support and manage Environment and Infra definition service variables override via git like we did in Current Gen for Next Gen. Like all users can pass the key value pair via json/yaml/properties file from Git to render the same in Harness.
Autopilot
Merged in a post:
convert values.yaml into variables or provide git support for variables definition
N
Novel Cod
Currently we can use variables in values.yaml. However not the other way. We can't take a value in values.yaml and convert into a Harness variable.
The motivation behind this would be, in a git based configuration and deployment management, you want all of your config to live in git and git in the only source of truth where you will making configuration changes.
values.yaml can be gitted. However variables can't be. This mean for a deployment, some attributes can live in git while some other (variable) can't. So to give a unified experience, it would be beneficial to either provide a git support for storing variables or allow converting values into variables.
Autopilot
Merged in a post:
Git Experience: Differences Between Resources
C
Charcoal Cheetah
The ability to edit git details is available for pipeline and templates. But for resources behind the feature flags (Services, Environments, Infrastructure definitions), this is not an option. Are there any plans to make these match in regards to their Git Experience features (as well as their respective REST APIs)?
Autopilot
Merged in a post:
Need yaml file / file storage section in overrides for environment variables
E
Eburnean Wallaby
In the Overrides section, we often find ourselves repeatedly creating environment-specific variables whenever a new environment is created and configured. We seek a solution to streamline this process by creating variable files or storing them separately, allowing us to efficiently reuse them for setting up any new environment.
Autopilot
Merged in a post:
Need GitX for Monitored service
R
Representative Llama
As of now, when we create a monitored service, we need to create it for per service per env basis. Any change that is done is restricted from the UI. This does not help in many of the cases like,
- In case of many(not all) services, monitored service rules are common, so doing the clonning and making change is not easier.
- Another issue is visibility/approvals of the change. audit trail might be there but it just simply can't beat the change review and history of git.
- For us user is used to do changes from the code, and moving to ui is not the ideal experience we want for the users.
We have checked the templates but it does not work as not all services required to have same metrics to observe. in some cases, use of diff language can also change how metrics are available. so keeping a template does not seem that useful currently.
One way sync has its own issues of time it takes and unavailability of the quick fix that can be done via the UI, so same arg as earlier but one way sync does not work.
Rohan Gupta
updated the status to
rejected
We will not be managing variables seperately in Git. The loading in the UI gets impacted as we continue to break down objects to be managed in Git. They are tied to Service, Pipeline, Templates already which are objects backed in Git.
Rohan Gupta
To be clear you want a configuration file that parses the Harness Variables out in a Key Value file. (i.e. JSON)
{
service-variables:
namespace: qa
service-name: seviceName
env-variables:
replica: 2
infra-variables:
cpu: 0.2
}
Load More
→