Multi-environments Management
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- kubernetes
- Domain
- devops
Research direction
The issue names no files, tests, or entry points. Start by reviewing how multiple GitOps connectors report status for the same repository and branch with separate dev/ and tst/ Kustomization paths. Done means the pipeline can distinguish and correctly handle each connector's status without requiring the tst path in the repository.
Written by the indexing model from the issue text.
Description
I would like to understand how to handle different environments with gitops connector?
The use case:
I have one kubernetes cluster for one environment (dev).
The repository contains one kustomization configuration (dev/).
In this scenario, everything works fine as I have one gitops connector that notifies the pipeline with its status.
Now, I want to introduce a new environment. I create another kubernetes cluster with another gitops connector.
I want to sync this cluster with the same repository & branch, only with another configuration (/tst)
I do not change anything on my repositor / branch (ie i don't create the kustomization configuration /tst)
Now, my pipeline sometimes works if it receives the dev gitops connector status, and sometimes fails if it receives the tst gitops connector status (as the kustomization path does not exist)
How to handle this scenario? ie how to properly get the status of each gitops connector in my pipeline?
Thank you for your help
- Dominant language
- Python
- Stars
- 142
- Forks
- 39
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure/gitops-connector
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Azure/gitops-connector#77 · 2 comments · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
Azure/gitops-connector#76 ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
Azure/gitops-connector#73 · 44 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
Azure/gitops-connector#66 · 1 comment · 1 reaction ·
All issues in Azure/gitops-connector
Similar issues
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
btclib-org/btclib-node#1955 ·
Maintainers usually reply within 1 day
-
documentation v0.9.2
Difficulty 2/5 Half a day Newbie friendliness 72/100
khuisman/mcp-gee-sweet#1033 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
ossf/cve-bin-tool#5966 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 2 days
-
write_iceberg ignores the table's write.parquet.compression-codec propertyPossibly taken @YuangGao claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Eventual-Inc/Daft#7606 ·
Maintainers usually reply within 1 day