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

[Merged by Bors] - feat(cdk): add -p package_name in cdk publish #3097

Closed
wants to merge 1 commit into from
Closed

[Merged by Bors] - feat(cdk): add -p package_name in cdk publish #3097

wants to merge 1 commit into from

Conversation

galibey
Copy link
Contributor

@galibey galibey commented Mar 23, 2023

Currently, cdk publish command does not have the option to specify the package; hence must be executed from the crate's directory. It is inconvenient in CI/CD pipelines.
This PR adds the support -p parameter so the command can be executed from any workspace directory.

This includes how files listed package-meta.yaml are searched: now they are looked up relative to the file package-meta.yaml itself instead of the current directory where cdk runs.

@galibey galibey requested review from digikata and sehz March 23, 2023 16:45
@galibey galibey self-assigned this Mar 23, 2023
@galibey galibey added the DX/CDK Connector Developer Kit label Mar 23, 2023
@galibey galibey added this to the 0.10.6 milestone Mar 23, 2023
Copy link
Contributor

@sehz sehz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM for CDK side. Will defer @digikata for hubutil

@digikata
Copy link
Contributor

The search assumption sounds reasonable to me.

@sehz
Copy link
Contributor

sehz commented Mar 23, 2023

bors r+

bors bot pushed a commit that referenced this pull request Mar 23, 2023
Currently, `cdk publish` command does not have the option to specify the package; hence must be executed from the crate's directory. It is inconvenient in CI/CD pipelines. 
This PR adds the support `-p` parameter so the command can be executed from any workspace directory.

 This includes how files listed `package-meta.yaml` are searched: now they are looked up relative to the file `package-meta.yaml` itself instead of the current directory where `cdk` runs.
@bors
Copy link

bors bot commented Mar 23, 2023

Build failed:

@sehz
Copy link
Contributor

sehz commented Mar 24, 2023

bors retry

bors bot pushed a commit that referenced this pull request Mar 24, 2023
Currently, `cdk publish` command does not have the option to specify the package; hence must be executed from the crate's directory. It is inconvenient in CI/CD pipelines. 
This PR adds the support `-p` parameter so the command can be executed from any workspace directory.

 This includes how files listed `package-meta.yaml` are searched: now they are looked up relative to the file `package-meta.yaml` itself instead of the current directory where `cdk` runs.
@bors
Copy link

bors bot commented Mar 24, 2023

Pull request successfully merged into master.

Build succeeded:

@bors bors bot changed the title feat(cdk): add -p package_name in cdk publish [Merged by Bors] - feat(cdk): add -p package_name in cdk publish Mar 24, 2023
@bors bors bot closed this Mar 24, 2023
@galibey galibey deleted the feat/cdk-publish-support-for-package branch March 24, 2023 10:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DX/CDK Connector Developer Kit
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants