Case fixes #1
Open
Case fixes #1
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
…for handling pull requests. Signed-off-by: John Dunham <[email protected]>
* Adding a ibm-spectrum-scale-csi-operator-dev.yaml to the generated YAML to facilitate better testing. * Change the linting sections in yaml to support molecule v3 * Fix linting errors on the osdk-scorecard.yaml file * Using a YAML formatter, fix the role.yaml file * Run the YAML formatter * Run the YAML formatter, fix linting errors * Using YAML formatter, Fix more linting errors in various files * More linting fixing * More linting issues * Fix playbook.yaml linting issues * disable line-length test on yamllint-er * Update the generated yaml based on the linting changes * Add YAML doc start. Remove hack to add dashes in generated yaml * Need better yamllint rules * missing newline at end of file * Linting issues with the yamllint file * More YAML Lint fixes * too many blank lines lint * Removing the docs build for now, I want to see molecule run * Let's try changing the operator.yaml file using a playbook insead of the Python Script * Fix the linting issues with the change_deploy_image file * Update the references to change_deploy_image.py to the playbook alternative * Leave off the other linters to get this back up and running * Removing funky character * Run the build docs again * Testing block in this playbook was formatted incorrectly * Need newling at end * Put the operator image back into a single line * Update the generated yaml file based on operator.yaml changes * Removing array from csv-path * Reinstating the tasks I accidentally removed in the merge. * Adding the missing CSI_DRIVER_IMAGE. * Fixing linter errors. * One Day I'll remember to run the generator. Co-authored-by: Victor Hu <[email protected]> Co-authored-by: Smita Raut <[email protected]>
Co-authored-by: Smita Raut <[email protected]>
Bumping up sidecar versions
* Resolves IBM#129 Added timeout parameter to provisioner and attacher command line and worker-threads parameter to the provisioner command line
snap changes
Fix provisioner name in examples
…umable steps to deploy in the README
…rhub and redhat certified bundles.
added 29 commits
April 14, 2020 08:30
…tion for the olm yaml files.
…i into case-fixes
Conflicts: generated/installer/ibm-spectrum-scale-csi-operator-dev.yaml generated/installer/ibm-spectrum-scale-csi-operator.yaml operator/deploy/olm-catalog/ibm-spectrum-scale-csi-operator/1.1.0/ibm-spectrum-scale-csi-operator.v1.1.0.clusterserviceversion.yaml operator/deploy/operator.yaml
Conflicts: .travis.yml operator/.osdk-scorecard.yaml
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.
Merging to fix the mistake I made doing stuff on a branch that was squash merged.
Minor fixes based on CASE PR feedback.