Payload encoding detection
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 974
- Forks
- 296
- Avg merge
- 6d 14h
- Merged PRs (30d)
- 9
Description
Feature Request
Environment
I'm using flatcar on Akamai Linode
Desired Feature
Payload is limited in size.
Currently, we are uploading ignition.json with a base64 encoding.
But it can be oversize the limit, so we are/want to use a gzip content.
I see VMware have already this:
https://github.com/coreos/ignition/blob/3b3a27b64541d01b7bb18f5f923ca3a13dcea98e/internal/providers/vmware/vmware.go#L33-L55
And other ticket are for specific providers #1096
Can we add a generic way to detect payload (b64 / gzip+b64 / zstd+b64...)
Other Information
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the provider-specific handling in internal/providers/vmware/vmware.go referenced by the issue, then compare the provider discussion in issue #1096. Determine the scope of provider-neutral payload detection and the supported encodings. Done means the agreed generic behavior is implemented and verified for the relevant payload forms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100