Conversation
|
🤖 Hey ! The @cpn-console/shared (v1.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/kubernetes-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 @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 @cpn-console/hooks (v4.0.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... |
Now that all our clusters are meant to be considered external, the property becomes useless. Everything will follow the GitOps route, from now on.
StephaneTrebel
force-pushed
the
suppression-code-suite-au-passage-en-gitops
branch
from
394590f to
c3d2a6a
Compare
|
🤖 Hey ! The security scan report for the current pull request is available here. |
|
0 New Issues
2 Fixed Issues
0 Accepted Issues1 participant
Issues liées
Issues numéro: #1883
Tous les clusters sont maintenant
external.Le passage en GitOps est terminé, il est temps de nettoyer tout ce qui n'a plus sa place.