forked from spinnaker/halyard
-
Notifications
You must be signed in to change notification settings - Fork 2
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
fix(validations): Request prototype bean from spring instead of using "new" #34
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
spinnaker#1376) * refactor(config): remove a pointless try/catch block * refactor(tests): remove an unused import * fix(config): parse 'oauthScopes' stanzas that were incorrectly written The old version of Lombok used in Halyard <=1.21 didn't copy @JsonProperty annotations to the generated methods. This means Jackson was seeing the field as 'oAuthScopes' and the getter/setter as a separate 'oauthScopes' property. The same data would be written to both properties, and during parsing whichever came last in the file would be persisted into the object. With new versions of Lombok (>=1.18.8), the @JsonProperty annotation is copied to the bean methods, so the 'oauthScopes' property disappears and Jackson can no longer parse those old files. This commit adds some methods to support parsing the files generated by previous versions of Halyard, but will no longer write out the incorrect duplicate data. * chore(copyright): add a missing copyright header
* feat(secret): decrypt secrets before sending to deck * code review changes
Remove the $REPO_NAME variable from the cloudbuild.yaml file; this is being used to decide the name of the image to push which will not always correspond to the image name. In particular, if we start publishing both alpine and ubuntu images we'll want the image name to have a suffix reflecting that.
* feat(plugins): adding halyard commands for plugins * chore(refactor): use toMap instead of a concurrentMap collector
* fix(kubernetes): Added support for tolerationn Signed-off-by: rverma-nikiai <[email protected]> * feat(kubernetes): Added support for Tolerations Added support for tolerations Signed-off-by: rverma-nikiai <[email protected]> * feat(kubernetes): Support for tolerations * fix(kubernetes): Added support for Tolerations, fixed access
… component sizing. (spinnaker#1387)
…spinnaker#1401) * refactor(deploy/kubernetes): Removed duplicated code * feat(deploy/kubernetes): Option to select the image variant to deploy Supports `slim` and `ubuntu`, the former being the default. Ubuntu image supported starting with v1.16.0.
…ounts (spinnaker#1420) * fix(provider/aws): Support for specifying lifecycle hooks for AWS accounts
…#1465) The slim/alpine image uses 1000/1000 as the uid and gid for the `spinnaker` user. Doing the same thing for the Ubuntu image makes it simpler for installers like the Helm chart to use either image variant.
…tor (spinnaker#1455) * fix(saml): get saml file path instead of file contents in saml validator * remove redundant SecretSessionManager
…pinnaker#1416) * feat(localfiles): Support relative local files to hal config home Usually when referencing local files in main hal config with a relative path, halyard throws this error: Problems in Global: ! ERROR Failed to backup user file: default/files/kubeconfig-main - Failed to generate config. With this change, relative files will be automatically resolved relative from hal config home. * feat(localfiles): Only prefix files in subdirectories of input prefix * feat(halyard/localfiles): Use getter for hal config directory * feat(halyard/localfiles): Error on relative files escaping hal home * feat(localfiles): Normalize path on comparison for removing prefix * chore(localfiles): Paths for building a path instead of string concat * chore(localfiles): Save field references to child nodes * chore(localfiles): Removed {%halconfig-dir%}, moved some code to parser * chore(localfiles): Support backups made with {%halconfig-dir%} * chore(localfiles): Support backups made with {%halconfig-dir%} * chore(localfiles): Using java Path instead of string handling * chore(localfiles): New FileService for getting file paths and contents * chore(localfiles): Use FileService for getting files
* feat(huaweicloud): first commit for huaweicloud r 3e29b2c feat(huaweicloud): first commit for huaweicloud r 14f49c4 feat(huaweicloud): add commands about account * feat(huaweicloud): add commands of account r 3e29b2c feat(huaweicloud): first commit for huaweicloud r 14f49c4 feat(huaweicloud): add commands about account * refactor(huaweicloud): add validator and change the way to input password * feat(huaweicloud): add commands of bakery * style(huaweicloud): add missed copyrights * style(huaweicloud): make code simple
…)" (spinnaker#1473) This reverts commit d35767d.
…ml (spinnaker#1456) manifest templates were adding unnecessary commas when podAnnotations, podLabels, or serviceLabels were supplied causing deployments to fail.
* feat(huaweicloud): first commit for huaweicloud r 3e29b2c feat(huaweicloud): first commit for huaweicloud r 14f49c4 feat(huaweicloud): add commands about account * feat(huaweicloud): add commands of account r 3e29b2c feat(huaweicloud): first commit for huaweicloud r 14f49c4 feat(huaweicloud): add commands about account * refactor(huaweicloud): add validator and change the way to input password * feat(huaweicloud): add commands of bakery * style(huaweicloud): add missed copyrights * style(huaweicloud): make code simple * fix(huaweicloud): fix the bakery validate exception
� Conflicts: � Dockerfile.ubuntu � docs/commands.md � gradle.properties � halyard-cli/src/main/java/com/netflix/spinnaker/halyard/cli/command/v1/ConfigCommand.java � halyard-cli/src/main/java/com/netflix/spinnaker/halyard/cli/command/v1/config/artifacts/gitrepo/GitRepoAddArtifactAccountCommand.java � halyard-cli/src/main/java/com/netflix/spinnaker/halyard/cli/command/v1/config/artifacts/gitrepo/GitRepoEditArtifactAccountCommand.java � halyard-cli/src/main/java/com/netflix/spinnaker/halyard/cli/services/v1/Daemon.java � halyard-config/src/main/java/com/netflix/spinnaker/halyard/config/config/v1/HalconfigDirectoryStructure.java � halyard-config/src/main/java/com/netflix/spinnaker/halyard/config/config/v1/HalconfigParser.java � halyard-config/src/main/java/com/netflix/spinnaker/halyard/config/model/v1/artifacts/gitrepo/GitRepoArtifactAccount.java � halyard-config/src/main/java/com/netflix/spinnaker/halyard/config/model/v1/node/Node.java � halyard-config/src/main/java/com/netflix/spinnaker/halyard/config/model/v1/node/Plugins.java � halyard-config/src/main/java/com/netflix/spinnaker/halyard/config/model/v1/node/Telemetry.java � halyard-config/src/main/java/com/netflix/spinnaker/halyard/config/model/v1/node/Validator.java � halyard-config/src/main/java/com/netflix/spinnaker/halyard/config/model/v1/util/ValidatingFileReader.java � halyard-config/src/main/java/com/netflix/spinnaker/halyard/config/validate/v1/canary/google/GoogleCanaryAccountValidator.java � halyard-config/src/main/java/com/netflix/spinnaker/halyard/config/validate/v1/security/SamlValidator.java � halyard-deploy/src/main/java/com/netflix/spinnaker/halyard/deploy/services/v1/GenerateService.java � halyard-deploy/src/main/java/com/netflix/spinnaker/halyard/deploy/spinnaker/v1/profile/KubernetesV2ClouddriverProfileFactory.java � halyard-deploy/src/main/java/com/netflix/spinnaker/halyard/deploy/spinnaker/v1/service/distributed/kubernetes/v2/KubernetesV2Service.java � halyard-deploy/src/main/java/com/netflix/spinnaker/halyard/deploy/spinnaker/v1/service/distributed/kubernetes/v2/KubernetesV2Utils.java
The title of the Pull Request needs to be changed. |
german-muzquiz
changed the title
Gen manifests extended validation
fix(validations): Request prototype bean from spring instead of using "new"
Jan 23, 2020
ncknt
approved these changes
Jan 23, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.