chore(update): gen-manifests update #52
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
Co-authored-by: Travis CI User <travis@example.org>
* chore(containers): tell curl to fail if it gets an HTTP error This will prevent errors from going unnoticed as happened with the missing AWS client. * chore(containers): Upgrade the bundled tools
…1565) * feat(stats): Rename telemetry to stats, enable by default * fix(stats): Rename TelemetryWrapper to StatsWrapper
Co-authored-by: Cameron Fieber <cfieber@netflix.com>
Co-authored-by: Travis CI User <travis@example.org>
…aker#1572) * feat(k8s/deploy): Add custom health check to service-settings. Need the ability to override the default commands created and populated in the Deployments readinessprobe. In our use case mTLS has been enabled and we need a way to modify the readiness probe in each service so that you can pass in the client certificate. By adding this functionality Halyard can support a much wider array of potential configurations for health checks for cases where a simple check of /health might not be desirable. * Update var to the correct generic type * fix(k8s/deploy): Update var to the correct generic type * chore(fix/style): ran spotlessJava to fix style issues
Co-authored-by: runner <runner@fv-az51>
Co-authored-by: runner <runner@fv-az50>
Co-authored-by: runner <runner@fv-az117.internal.cloudapp.net>
Co-authored-by: runner <runner@fv-az76>
Co-authored-by: runner <runner@fv-az51>
…pinnaker#1580) This reverts commit fd2ef27.
Slack is littered with people having this issue. It looks like this was added in halyard 1.23 on 8/27/2019. So anyone with a config after that will have this issue.
…pinnaker#1584) The mergify config currently doesn't distinguish between merging to master and merging to a release branch. It currently never merges to release branches because mergify doesn't have permission to merge to these branches (due to branch protection rules). I don't want to give mergify that permission without updating the config file here, as then it would merge to release branches after any approval, whereas we only want to merge to release branches if a PR is approved by a release manager. This updates the mergify config to scope the existing rules to only apply to the master branch, and adds a new rule to merge to release branches upon approval by a release manager. Because the 1.17 branch (and likely the 1.18 branch in some repos) is still exclusively using Travis CI instead of github actions, also add a rule the merges if Travis CI passes to account for these branches. This rule can be deleted once all of the active branches in the repo are using Github actions. Co-authored-by: Michael Plump <plumpy@google.com>
Co-authored-by: runner <runner@fv-az33>
Co-authored-by: runner <runner@fv-az51.internal.cloudapp.net>
* fix(plugins): changing plugin-manifest.js to .json file type * fix(plugins): remove comments from json file, handle multiple plugins
* feat(plugins): add plugins to all services * refactor(plugins): remove introspection * refactor(plugins): change Boolean to boolean
Co-authored-by: runner <runner@fv-az118.internal.cloudapp.net>
Co-authored-by: runner <runner@fv-az51>
…innaker#1590) This change breaks deploying any version of Spinnaker <= 1.18 using Halyard, so is being reverted. This reverts commit 4ed4d26.
Co-authored-by: runner <runner@fv-az51>
Co-authored-by: runner <runner@fv-az51>
Co-authored-by: runner <runner@fv-az51>
Co-authored-by: runner <runner@fv-az51>
* feat(plugins): add plugins to all services * fix(regression): update version check to handle non-semver releases * fix(plugins): do not deploy to kayenta until 1.20.0
…naker#1798) Reverts spinnaker#1724 (which itself was a rollback of spinnaker#1653 and spinnaker#1663) to turn this back on.
Co-authored-by: root <root@1c964967be5d>
Co-authored-by: root <root@bcaea77c9d18>
Co-authored-by: root <root@96ca2b2c6285>
Halyard compiles to Java 11 as of spinnaker#1802.
Co-authored-by: root <root@28bd9d7e8d49>
…ct (spinnaker#1806) The `kubernetes-spinnaker` project seemingly exists solely to host this one image. I have no idea why. Let's move it into its own Artifact Registry repository in the CDF-owned `spinnaker-community` project. Also, the version of Redis in this image is 3.2.11, which is three years old, but I suppose that's a problem for another day.
…ing roles. (spinnaker#1805) * feat(aws): adding externalId command and field for aws account config * chore(aws): better definition for the new property external Id Co-authored-by: Justin Field <justin.field@armory.io>
Co-authored-by: root <root@6a7b3894974d>
Co-authored-by: root <root@b272e1bb32f7>
Co-authored-by: root <root@5900c8b382c3>
Required a few manual changes because of spinnaker/kork#783
Co-authored-by: root <root@44bc22e6f2e4>
Co-authored-by: root <root@2897678eb22e>
Co-authored-by: root <root@877703f80d77>
Co-authored-by: root <root@c51049d641bc>
Co-authored-by: root <root@893456aa42c8>
Co-authored-by: root <root@e9b0b38e4e5f>
Co-authored-by: root <root@9c1f95bcaee1>
Co-authored-by: root <root@73fd689d0395>
…nnaker#1820) Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
# Conflicts: # Dockerfile.slim # Dockerfile.ubuntu # README.md # build.gradle # docs/commands.md # gradle.properties # gradle/wrapper/gradle-wrapper.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/services/v1/Daemon.java # halyard-config/halyard-config.gradle # halyard-config/src/main/java/com/netflix/spinnaker/halyard/config/config/v1/ArtifactSourcesConfig.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/services/v1/FileService.java # halyard-config/src/main/java/com/netflix/spinnaker/halyard/config/validate/v1/providers/cloudfoundry/CloudFoundryAccountValidator.java # halyard-deploy/src/main/java/com/netflix/spinnaker/halyard/deploy/config/v1/secrets/DecryptingObjectMapper.java # halyard-deploy/src/main/java/com/netflix/spinnaker/halyard/deploy/services/v1/DeployService.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/KubernetesV2RedisService.java # halyard-web/config/halyard.yml # install/Installer.sh # release/docker.sh
dogonthehorizon
approved these changes
Nov 11, 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.