Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ftl new go should explain envar usage for platforms #2938

Closed
matt2e opened this issue Oct 1, 2024 · 3 comments
Closed

ftl new go should explain envar usage for platforms #2938

matt2e opened this issue Oct 1, 2024 · 3 comments
Assignees

Comments

@matt2e
Copy link
Collaborator

matt2e commented Oct 1, 2024

GOOS and GOARCH should be mentioned in the help text

@github-actions github-actions bot added the triage Issue needs triaging label Oct 1, 2024
@matt2e matt2e self-assigned this Oct 1, 2024
@github-actions github-actions bot removed the triage Issue needs triaging label Oct 1, 2024
@ftl-robot ftl-robot mentioned this issue Oct 1, 2024
@alecthomas
Copy link
Collaborator

We don't want users to use these actually, we want it to be reflected from the clsuter.

@matt2e
Copy link
Collaborator Author

matt2e commented Oct 2, 2024

Is that happening soonish do you think? One of the loose ends with the language plugin stuff is to make sure envars gets passed alongand I think this was the main use case for that

@stuartwdouglas
Copy link
Collaborator

AFAIK the main usage of this currently is to run the kube tests locally on a MBP. Once we have #1845 I don't think there will be any real need for the user to know about these.

@matt2e matt2e closed this as completed Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants