Skip to content

Read the client's platform (os and arch) from actions #1595

@samalba

Description

@samalba

In order to replace certain tasks implemented with make or other scripts that runs on your host machine, it's a must-have to have access to the client's OS and Platform.

For instance: #1589 - It implements basic actions ported from the Makefile. Since all actions commands run within linux containers, every binary produced will be ELF, not usable from the Mac where I run dagger up. It would be an easy fix if the action had access to the client platform and os so it can cross compile.

Example:

package engine

#Plan: {
	inputs: {
		...
	}
	outputs: {
		...
	}

	// Holds client related information
	client: {
		architecture: string
		os: string
	}

	actions: {
		...
	}
}

Related to: #1522 #1549

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions