bundle migration #67
Merged
bundle migration #67
Conversation
This file contains hidden or 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
Member
leifmadsen
commented
Oct 1, 2020
leifmadsen
commented
- Migrate latest CSV to manifests directory
- Create initial bundle
- Update Travis-CI to check bundle validation
- No automatic releases for right now
- Add new README.md for release process
- Be verbose when checking bundle validation
- Update build/README.md for validation command
- Smart Gateway Operator v2.0.1 is the base release
Migrate latest CSV to manifests directory in preparation for migrating to the bundle release format vs the application registry approach. Update the operator.yaml which was out of sync with the latest CSV. Latest CSV has been updated to sync with the operator.yaml which has the current container image tags applied to the CSV which was incorrect.
Remove the replaces line from the CSV to start our base release for bundles as the most current release. From here we will create new CSVs that will replace starting at v2.0.1 rather than having to import all the historical CSVs which are not used by anyone.
csibbitt
approved these changes
Oct 1, 2020
| - /tmp/ansible-operator/runner | ||
| - stdout | ||
| image: quay.io/infrawatch/smart-gateway-operator:latest | ||
| image: quay.io/infrawatch/smart-gateway-operator:v2.0.1 |
| maturity: alpha | ||
| provider: | ||
| name: Red Hat | ||
| replaces: smart-gateway-operator.v2.0.0 |
Contributor
There was a problem hiding this comment.
I assume this was intentional and is no longer necesarry?
Member
Author
There was a problem hiding this comment.
Yea sorry it was in the last commit. As part of the bundle migration I'm going to set v2.0.1 as the "base" version. When I create a new SGO / SG release that replaces line will come back.
I was avoiding having to create bundles for all CSVs back to 0.2.0 since that kind of just seemed silly.
Member
Author
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.