Remove leftover openstack code #778
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
There are still remnants of openstack in the Bandit code base. Namely there was still a coverage step that relied on a openstack git repo. Bandit is self contained and no longer only part of the openstack ecosystem. Therefore it's safe to remove this coverage step (which wasn't run anyway). Signed-off-by: Eric Brown <browne@vmware.com>
ericwb
requested review from
ghugo,
lukehinds and
sigmavirus24
as code owners
sigmavirus24
approved these changes
Jan 25, 2022
lukehinds
approved these changes
Jan 25, 2022
This was referenced Jan 25, 2022
This was referenced Feb 28, 2022
This was referenced Mar 7, 2022
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.
There are still remnants of openstack in the Bandit code base.
Namely there was still a coverage step that relied on a openstack
git repo. Bandit is self contained and no longer only part of the
openstack ecosystem. Therefore it's safe to remove this coverage
step (which wasn't run anyway).
Fixes Issue #297
Signed-off-by: Eric Brown browne@vmware.com