Orbs

Team, I did reach out to circle ci customer support for configuring slack notification on workflow fail/ pass. But after trying multiple solutions provided by Josh and team, we failed to achieve it. So please provide this feature. Requirement: Slack notification on workflow fail/ pass event Use case: Regression has multiple job setup to execute automation test cases in 5 containers. So once this jobs are completed I would like to receive a notification each job status in one line expected output: workflow master-regression failed Jobs: goals2019 - failed, rtf email_rtf- passed, profile- failed

Status badges are only available for public orbs at the moment. Similar to the API token used for pipeline status badges, can we get this functionality for private orbs

Recently I learned of the circleci/path-filtering orb that uses the continuation API in a Setup Workflow. This is a really powerful set of tools, except for some reason the base-revision is not something that can be dynamically controlled. While you can set the base-revision for the path filtering orb to any valid value, including other parameters, it is not possible to dynamically create a value for the base-revision. For example, if the base-revision is set to a value of master it works fine. But if we create a pre-step that gets the base revision from Github, the value cannot be used as the base revision. Relying on the pipeline.git.base-revision as a dynamic revision is not reliable, and doesn't work the way one might hope it would. In practice this means that developers using CircleCI in my project need to manually update the base-revision whenever they are working on a different base from main / master . Can the orb be updated to accept an environment variable exported into $BASH_ENV from a pre-step, or can we have some other mechanism for dynamically controlling this parameter? Ideally I would be able to do something like this version: 2.1 setup: true orbs: path-filtering: circleci/path-filtering@0.0.2 workflows: generate-config: jobs: - path-filtering/filter: pre-steps: - run: name: Fetch Base Branch from Github command: | BASE_BRANCH=$(curl -X GET \ -H "Authorization: token $GITHUB_TOKEN" \ -H "Accept: application/vnd.github.groot-preview+json" \ -L "https://api.github.com/repos/$CIRCLE_PROJECT_USERNAME/$CIRCLE_PROJECT_REPONAME/commits/$CIRCLE_SHA1/pulls" \ | jq '.[].base.ref') echo "export BASE_BRANCH=$BASE_BRANCH" >> $BASH_ENV base-revision: $BASE_BRANCH mapping: | path/to/dir/.* build-my-job true Path Filtering orb https://circleci.com/developer/orbs/orb/circleci/path-filtering

I'm reaching out to request enhancements to CircleCI in two key areas that would significantly improve our workflow flexibility and configuration management. Feature 1: Passing Arguments on the Orb Level I propose the introduction of a feature that allows passing arguments on the orb level or, at the very least, passing a list to an orb job. This enhancement would provide users with greater control and customization when utilizing orbs within their configuration files. I saw that a similar request for passing list was proposed before but no actions seems to be taken. Feature 2: Dynamic Job Creation Our team frequently uses the Helm template to dynamically build our CircleCI configuration. It would be immensely valuable if CircleCI supported dynamic job creation. For example, we have a job named "Integration Test" where users can specify Docker containers to enable. With dynamic job creation, users could pass parameters like: mongo: enabled: true kafka: enabled: true And the generated job would reflect these parameters: integration-test: docker: - image: mongo:latest - image: kafka:latest - etc... These enhancements would significantly improve our ability to manage and customize workflows, leading to a more streamlined and efficient CI/CD process. Thank you for your time and consideration. We believe these enhancements would greatly benefit the CircleCI community and look forward to your feedback.

Hey all, Is there any means to turn our public orb to private orb please ?

Unpublished orbs should have a grace period in which the name can be modified and the orb can be switched between public and private, in case an error was made during creation

It would be nice if CircleCI automatically scanned config files and notified users when new versions of orbs are published -- a sort of dependabot for orbs.

We're encountering more use cases where customers want centrally managed configurations that can be called and used. For example, many projects may follow the exact same workflows, and any updates to a process need to be reflected in all projects. Orbs are a step in the right direction, but each project must still manually update the orb version to see new changes - a centralized change does not propagate automatically. Maybe if we added a "latest" tag for orbs? We also don't yet support templatizing workflows in orbs, so we still have to write a lot of config. Related ideas: https://ideas.circleci.com/orbs/p/workflows-in-orbs

We are interested in the ability to parameterize contexts within an orb so that we can switch between contexts.

We've started using custom orbs, these define a base image, say cimg/clojure:<tag>. We'd like to also offer executors with common tools, Localstack, MinIO, Redis, Postgres, etc. However there's no way of adding additional images to an executor currently. I'd suggest one of two solutions: Allow executors to have more images provided via parameters. Right now it isn't possible to have a when block in the executor config, or extend the executors Extend executor image config when specifying it, rather than replacing it. This would be a breaking change so it would likely need to be under a separate executor parameter, rather than docker Right now we're creating two executors, one with just the main runner for the core language, and another with Localstack and Minio, which is our common setup. If we ever need more docker images, we need to copy and paste that config from the orb for all the images.