This repository has been archived by the owner on Oct 22, 2021. It is now read-only.
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.
Replaces v15.1.0, which was never used except by an abandoned attempt to bump kubecf to v15.1.0, which
simply was the latest release at the time the attempt was made.
Pipeline on flintstone has already been updated with this change. Somewhat surprised to see some unrelated changes like adding
check_every: 5m
to many resources.Exception are the
s3
resources, which had their check interval changed from1m
to10m
.The
prepare-build
job says:There are releases which are no longer part of cf-deployment: cf-syslog-drain
Is this something that should be dealt with in the pipeline?