Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

❗ NOTICE (pipelines): step id cannot be unresolved error during synthesis #27701

Closed
vinayak-kukreja opened this issue Oct 26, 2023 · 2 comments
Assignees
Labels
@aws-cdk/pipelines CDK Pipelines library management/tracking Issues that track a subject or multiple issues p0

Comments

@vinayak-kukreja
Copy link
Contributor

vinayak-kukreja commented Oct 26, 2023

Please add your +1 πŸ‘ to let us know you have encountered this

Status

In-Progress

What is the issue?

A fix change to the pipelines module appended the branch name onto the node id and input/output artifacts. This leads to an error during synthesis if the value being substituted is a Token.

Error message

During synthesis, you can see `Step id cannot be unresolved` error.

What is the impact?

Synthesis for the module would not work in some cases.

Workaround

You can migrate back to cdk version <= 2.102.1

Who is affected?

Users will be impacted, if the repo and/or branchName is a Token.

How do I resolve this?

The impacting PR has been reverted and a new patch release (v2.103.1) is now out.

Related issues

No response

@vinayak-kukreja vinayak-kukreja added management/tracking Issues that track a subject or multiple issues p0 @aws-cdk/pipelines CDK Pipelines library labels Oct 26, 2023
@vinayak-kukreja vinayak-kukreja pinned this issue Oct 26, 2023
@vinayak-kukreja vinayak-kukreja self-assigned this Oct 26, 2023
@vinayak-kukreja vinayak-kukreja changed the title ❗ NOTICE (pipelines): step id cannot be unresolved during synthesis ❗ NOTICE (pipelines): step id cannot be unresolved error during synthesis Oct 26, 2023
mergify bot pushed a commit to cdklabs/aws-cdk-notices that referenced this issue Oct 26, 2023
@vinayak-kukreja
Copy link
Contributor Author

The impacting PR has been reverted and a new patch release (v2.103.1) is now out.

@github-actions
Copy link

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
@aws-cdk/pipelines CDK Pipelines library management/tracking Issues that track a subject or multiple issues p0
Projects
None yet
Development

No branches or pull requests

1 participant