Request: move `internal/computecore` and `internal/hcs` out of `internal/`

Open
#2,823 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
52/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
go
Domain
api

Research direction

Start with internal/computecore/computecore.go and the internal/hcs/... packages, then trace how they are used by callers of the HCS API. Work out the public package layout and the changes needed to move these packages without requiring third-party applications to copy them. Done means those applications can import the packages from outside internal/.

Written by the indexing model from the issue text.

Description

https://github.com/microsoft/hcsshim/blob/main/internal/vmcompute/vmcompute.go https://github.com/microsoft/hcsshim/blob/main/internal/computecore/computecore.go is useful for third-party applications that call the HCS API.

Would it be possible to move internal/vmcompute internal/computecore (and ideally internal/hcs/... too) out of internal/ so that third-party applications can use this package without copying it?

Dominant language
Go
Stars
694
Forks
304
Avg merge
1d 19h
Merged PRs (30d)
28

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/hcsshim

All issues in microsoft/hcsshim

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.