-
Notifications
You must be signed in to change notification settings - Fork 4
refactor vault Plugin to remove AppRole enabled check and clarify separated classes #1835
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor vault Plugin to remove AppRole enabled check and clarify separated classes #1835
Conversation
|
🤖 Hey ! The @cpn-console/vault-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. |
|
🤖 Hey ! The @cpn-console/harbor-plugin (v2.2.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/gitlab-plugin (v3.3.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/sonarqube-plugin (v2.0.5) 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... |
|
StephaneTrebel
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
| import monitor from './monitor.js' | ||
| import { VaultProjectApi, VaultZoneApi } from './class.js' | ||
| import { VaultProjectApi } from './vault-project-api.js' | ||
| import { VaultZoneApi } from './vault-zone-api.js' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
praise: C'est beau !
| private readonly roleName: string | ||
| private readonly projectRootDir: string | ||
| private readonly defaultAppRoleCredentials: AppRoleCredentials | ||
| private readonly coreKvName: string = 'forge-dso' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thought: Rien à voir avec cette MR, mais cette valeur en dur me dérange à plus d'un titre
| this.defaultAppRoleCredentials = { | ||
| url: getConfig().deployVaultConnectionInNs ? getConfig().publicUrl : '', | ||
| coreKvName: this.coreKvName, | ||
| roleId: 'none', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
question: Je sais que c'était comme ça auparavant, mais est-ce que ce n'est pas un problème ? 'none' ce n'est pas un roleId, en soi. undefined (et un typage adapté) eut probablement été plus clair, non ?
|
🤖 Hey ! A preview of the application is available at : https://console-pr-1835.dso.cpin-hp.numerique-interieur.fr Please be patient, deployment may take a few minutes. |
|

0 New Issues
0 Fixed Issues
0 Accepted Issues
No data about coverage (71.90% Estimated after merge)
Issues liées
Issues numéro: #1829
Quel est le comportement actuel ?
Quel est le nouveau comportement ?
Cette PR introduit-elle un breaking change ?
Autres informations