feat: ✨ store cluster secret in Vault #1504
Conversation
|
🤖 Hey ! The @cpn-console/argocd-plugin (v2.1.3) 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/vault-plugin (v2.2.1) 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/gitlab-plugin (v2.4.3) 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 (v2.5.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. |
mathieulaude
force-pushed
the
feat/kubeconfig-in-vault-2
branch
from
98d9f2c to
462f29f
Compare
|
🤖 Hey ! The @cpn-console/shared (v1.2.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... |
mathieulaude
force-pushed
the
feat/kubeconfig-in-vault-2
branch
from
462f29f to
cea79ef
Compare
|
🤖 Hey ! The @cpn-console/kubernetes-plugin (v2.1.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/harbor-plugin (v2.2.2) 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/nexus-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... |
|
Issues liées
Issues numéro:
Quel est le comportement actuel ?
Quel est le nouveau comportement ?
Cette PR introduit-elle un breaking change ?
Autres informations