feat: ✨ distinguish between public and internal gitlab url #1791
Conversation
|
🤖 Hey ! The @cpn-console/gitlab-plugin (v3.3.0) package already exists on npm but the source code has changed, you should consider updating the package version. The version update warning should be ignored in the case of modifications that do not affect the code once it has been built, such as code formatting, etc... |
|
🤖 Hey ! The @cpn-console/argocd-plugin (v2.3.0) package already exists on npm but the source code has changed, you should consider updating the package version. The version update warning should be ignored in the case of modifications that do not affect the code once it has been built, such as code formatting, etc... |
|
🤖 Hey ! The security scan report for the current pull request is available here. |
Falltrades
force-pushed
the
feat/distinguish-public-internal-url
branch
from
a472e3f to
6718dca
Compare
|
0 New Issues
0 Fixed Issues
0 Accepted Issues
No data about coverage (73.50% Estimated after merge)
Issues liées
Issues : cloud-pi-native/socle#765
Quel est le comportement actuel ?
Our achitecture design is allowing to have other Argocd located in a separate cluster. Thus, the communication can only be done through ingress.
Quel est le nouveau comportement ?
We are distinguishing public and internal gitlab url because we can still use internal url for Gitlab runner jobs.
Cette PR introduit-elle un breaking change ?
No.
Autres informations
Related to 9e8835b