Move triggers to GitEx
long-term
Log In
Rohan Gupta
Merged in a post:
Git Experience and Triggers
P
Polite Tortoise
Looking at the Git Experience for Harness resources here: https://developer.harness.io/docs/platform/git-experience/configure-git-experience-for-harness-entities/
It does not currently support Triggers. Is there any work to get these added or is there some kind of restriction?
Rohan Gupta
Merged in a post:
Support for storing triggers on Git
I
Increased Bison
Currently, there is no support for storing triggers on Git. It would be beneficial to have this feature to streamline the process and maintain consistency with other Harness objects. This feature would enhance the Git experience by allowing users to manage triggers alongside other entities in their repositories.
F
Frequent Jay
Any update? Bizzare that this isn't supported
Rohan Gupta
Merged in a post:
Saving trigger yaml into git repo
M
Marigold Lizard
Hi Support,
Could you provide a feature that saves trigger yaml into source control? such feature are provided for pipeline yaml and inputset yaml, why not have it for trigger yaml as well.
Thanks and Regards
Naichen
Canny AI
Merged in a post:
best ways to keep input set and trigger in code
S
Sharp Swift
The changes of the pipeline studio are tracked into the git connector. that feature is nice as it track any changes and code it.
the problem is when we add a new input trigger or a new trigger. nothing bieng track into code. we can somehow view the YAML view of it.
is there any ideas that help to automatically push changes to git of Triggers and Input sets ?
E
Ebony Ocelot
Hi Team,
Please try to prioritize this request, we also have additional reuirement to store connectors configuration in git.
Rohan Gupta
Merged in a post:
yaml secrets
R
Raspberry Grouse
Harness allows us to store Pipelines, InputSets, and Services in GitHub, but Triggers and Secrets are not. Is this feature coming soon? Since we can use the YAML Generator to create these items, it would be very beneficial to keep them in github with the rest of the 'setup as code', especially for DR purposes, but also because it gives us the ability to have more self-service options for non-devops people.
Rohan Gupta
Merged in a post:
Support Triggers as part of the Git Experience
F
Frequent Jay
Just like other entities We need support to store and use triggers as part of the Git Experience.
Sudarshan Purohit
Hi Sharp Swift, Input Sets are supported as remote entities (i.e. synced with Git), if the Pipeline is already remote. However, Triggers are not currently supported as remote entities.
Some of our users have set up one way syncs from Git to Harness, where the Trigger YAML is stored in Git, and then a script is used to automatically push updated YAML from Git to Harness whenever the YAML changes. This one way sync could also be done using Terraform provisioning. Potentially you could follow that approach?
S
Sharp Swift
Sudarshan Purohit Thanks Sudarshan Purohit. Yes im interested to know about the sync approach. should i use this thread or create another ticket? as for Terraform its not viable from my team since it requires major changes.
Sudarshan Purohit
Sharp Swift: Sure, let me reach out to our team, and we'll connect with you on setting this up.
S
Sharp Swift
Sudarshan Purohit sounds good. i will wait
F
Fawn Antelope
Yes please!
Load More
→