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

feat: --private-key option should not only support paths #25

Open
robingenz opened this issue Jan 8, 2025 · 1 comment
Open

feat: --private-key option should not only support paths #25

robingenz opened this issue Jan 8, 2025 · 1 comment
Assignees
Labels
feature Feature

Comments

@robingenz
Copy link
Member

It should be possible to pass the private key directly when using the --private-key option.

Example:

- name: Create a bundle on Capawesome Cloud
  run: npx capawesome apps:bundles:create --appId "..." --path www --private-key ${{ secrets.CAPAWESOME_CLOUD_PRIVATE_KEY }}
@robingenz robingenz added the feature Feature label Jan 8, 2025
@robingenz robingenz self-assigned this Jan 8, 2025
@robingenz
Copy link
Member Author

robingenz commented Jan 8, 2025

Update: Unfortunately, this is currently not possible because citty interprets strings that start with - as booleans.

{
  _: [],
  'private-key': true,
  B: true,
  E: true,
  G: true,
  I: true,
  N: true
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Feature
Projects
None yet
Development

No branches or pull requests

1 participant