Improve identification when an orb is "unused" if it's executor is used
complete
A
Adam Harvey
In our pipeline, we use the CLI Orb to define an executor, and then use that executor in jobs. Interestingly, we've found v1.2 of the VS Code extension warns us that the CLI orb is unused. But if we remove it, then the warning shows up on any job where we have defined the executor as "executor: cli/default" with "Executor
cli/default
does not exist" (which is now correct).So we believe the error that the orb is not in use isn't quite right in this instance, if we're using the executor from the orb. (Which to be fair, does seem like an edge case!)
Reproducible YAML:
version: 2.1
orbs:
# see warning about orb not in use
cli: circleci/circleci-cli@0.1.9
jobs:
do-stuff:
# if orb is commented out, this line will warn the executor is unknown
executor: cli/default
steps:
- checkout
workflows:
my-workflow:
jobs:
- do-stuff
B
Benedetta Dal Canton
complete
B
Benedetta Dal Canton
Hi Adam Harvey, I just wanted to let you know that we've just release a new version of the extension (1.6.0) which fixes this problem.
We've also introduced the possibility of always keeping the default branch on display, while monitoring a specific branch (or the current branch). I remember you mentioning that this might be useful to you and your team back when we spoke in November, so figured I'd let you know!
And support for monitoring multiple projects at the same time is coming in the near future, stay tuned!
Let me know if you have any other suggestions or issues in using the extension, I'm always available to chat!
Adam Harvey
Benedetta Dal Canton: Thank you to you and the team! I've tested v1.6, and confirmed it fixes the functionality listed in this idea. Think this idea is a good one to mark closed! :clap:
B
Benedetta Dal Canton
Hi Adam, Thank you very much for flagging this.
I've shared it with the team and we'll look into it soon!