This repository has been archived by the owner on Feb 10, 2022. It is now read-only.
Merge kubo-deployment into kubo-release #404
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
Signed-off-by: Neil Hickey <nhickey@vmware.com>
Signed-off-by: Neil Hickey <nhickey@vmware.com>
Signed-off-by: Neil Hickey <nhickey@vmware.com>
Signed-off-by: Neil Hickey <nhickey@vmware.com>
- Also removes unit-tests as these are now covered by Github Actions Signed-off-by: Neil Hickey <nhickey@vmware.com>
Signed-off-by: Neil Hickey <nhickey@vmware.com>
Signed-off-by: Neil Hickey <nhickey@vmware.com>
Signed-off-by: Neil Hickey <nhickey@vmware.com>
neil-hickey
force-pushed
the
merge-kubo-deployment
branch
from
73ce0fa
to
01f8a7e
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What this PR does / why we need it:
This PR merges the https://github.com/cloudfoundry-incubator/kubo-deployment repo into this repo
Why?
kubo-deployment currently is purely for the manifest / ops-files needed to deploy CFCR. To reduce the maintenance burden / make it easier to see all the moving parts, this PR is intended to remove that repo and consolidate
Is there any change in kubo-deployment?
This PR removes the need for this other repo
Does this affect upgrade, or is there any migration required?
No, this PR should not affect upgrades. It just moves the ops-files and the main bosh deployment manifest to this repo.
Which issue(s) this PR fixes:
#403
Release note:
What is being done?: