-
The test coverage for EC2 metadata endpoints needs evaluating as it seems incomplete. This was identified when refactoring code in https://github.com/tinkerbell/hegel/pull/139
-
## Expected Behaviour
Metadata (from the metadata package) is typed within the Hardware type used by the Hardware client.
```go
import (
"github.com/tinkerbell/tink/protos/hardware…
-
Tracking and discussion issue for 0.9.
-
Users sometimes only care about backward compatibility or new features. Setting up the CI to create tags that include only Major and Major.Minor will ensure they always pull the latest Minor.Patch and…
-
## Expected Behaviour
Smooth `vagrant up` for _provisioner_.
## Current Behaviour
What I got:
```text
...
provisioner: node/k3d-k3s-default-server-0 condition met
provisi…
-
### Bug Description
Thank you for helping out with the last issue!
Yet still a little problem. I find strange things occur every time I press opt+enter on an entry, no pop-up window, nothing is copi…
-
I am using the hardware and template examples as outlined on the tinkerbell.org documentation page. I have found that when rootio requests metadata from hegel, it is expecting it in a format that i…
-
I'm trying to install the provisioner on a server behind a proxy.
It is not functioning because, in spite the fact that I've already set the proxies variables both in the environment and also into th…
-
The typescript type system is helpful in most cases, but it can’t be utilized when handling exceptions.
For example:
```
function fn(num: number): void {
if (num === 0) {
throw "error…
-
## Proposal: A built-in Go error check function, `try`
**This proposal has been [closed](https://github.com/golang/go/issues/32437#issuecomment-512035919). Thanks, everybody, for your input.**
B…