Orb version:

latest

What happened:

The dev version of myorg/cdk@dev:alpha has expired. Dev versions of orbs are only valid for 90 days after publishing.

Expected behavior:

it should build as it did in the first 90 days. what do we need to do to recover from this error?

Additional Information:

Orb version:

1.1.4

What happened:

Packing and validating this repo gives an error referencing the shell script:

$ circleci config pack src | circleci orb validate -

Error: Error calling command: 'greet'
Unclosed '<<' tag in string: '<<include(scripts/greet.sh)>>'
('<<' must be escaped as '\<<' in config v2.1+)
Error calling job: 'hello'
Error calling command: 'greet'
Unclosed '<<' tag in string: '<<include(scripts/greet.sh)>>'
('<<' must be escaped as '\<<' in config v2.1+)

Expected behavior:

The orb should validate successfully.

Additional Information:

$ circleci version

0.1.11458+44f80c2 (homebrew)

Provide a comment on shell usage for different languages in scripts/README.md: https://github.com/CircleCI-Public/Orb-Project-Template/tree/master/src/scripts

ex:

steps:
  - run:
      environment:
        PARAM_TO: <<parameters.to>
      name: Hello <<parameters.to>
      shell: /bin/sh  # Not required for shell scripts, but useful for other shell environments i.e. python
      command: <<include(scripts/greet.sh)>>

This would help users who may expect the included script to execute without declaring the shell parameter: #25

Major shellcheck orb update coming with the release of the Orb Pack command

Orb version: 2.1

Cloned this repo and attempted to pack and validate

What happened:

Expected behavior:

It should validate successfully

Is there a way we can get the new orb badge in here in order to promote its usage?

Orb version:

What happened:

The job orb-tools/dev-promote-prod-from-commit-subject on integration-test_deploy workflow on Circle CI configuration doesn't work for the new repository, because since October 1, GitHub allows developers to set default branch, and the default value of it is main, not master.

Expected behavior:

circleci orb init allows us to set the default branch.

Additional Information:

Describe Request:

Similar to CircleCI-Archived/orb-starter-kit#44 - occasionally, orb dev:alpha versions will expire, which means that future commits for that orb will fail the pipeline. Ideally, we set up a cron job within the configuration to automatically refresh this version every 90 (or 89?) days.

Describe Request:

Make this a template repository in GitHub settings to allow use this template option from GitHub

Supporting Documentation Links:

https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/creating-a-template-repository

Orb version:

Which orb?

What happened:

When using the Orb-Project-Template, if you create a commit for the orb you are working on that contains both a new command or job and an integration test for it, workflow execution will fail with a message similar to:

Error calling workflow: 'integration-test_deploy'Error calling job: 'integration-test-3'Cannot find a definition for command named cci-orb/test2

Expected behavior:

Being able to add a command and a test for it in the same commit.

If that is not possible to fix, clear documentation about this limitation in the readme would be appreciated.

Additional Information:

The workaround I've been using is to add another commit with the test removed from .circleci/config.yml and push it. Once that has been built and deployed you can then drop the commit, force push and finally get to where you wanted to be in the first place.

Looks like other people are also encountering the problem for example https://discuss.circleci.com/t/jobs-in-private-orbs-not-recognized-by-integration-tests/42812

Describe Request:

Allow to execute python script command like actually do with bash.

Example:

`
parameters:
to:
type: string
default: "World"
description: "Hello to whom?"
steps:

• run:
  environment:
  PARAM_TO: <<parameters.to>>
  name: Hello Greeting
  command: <<include(scripts/greet.py)>>
  `