aws / aws/aws-nitro-enclaves-cli

Question about crate publishing status

Open
#706 0 comments 1 reaction 0 assignees View on GitHub
Dominant language
Rust
Stars
156
Forks
99
PR merge metrics
No merged PRs in 30d

Description

Is there a technical reason why the `nitro-cli` crate isn't published as a public crate, unlike other AWS Nitro related crates like `aws-nitro-enclaves-nsm-api` and `aws-nitro-enclaves-image-format`?
Consuming the crate via git + git tags is less elegant and can run into issues, as seen in #705.

Contributor guide

Open the contributing guide

Research direction

The issue names the nitro-cli crate and the public aws-nitro-enclaves-nsm-api and aws-nitro-enclaves-image-format crates; start by comparing their crate metadata and publishing configuration. Done means documenting the technical reason for git-tag consumption or publishing nitro-cli publicly with an agreed release path.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
release
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.