From 73c7b56600e71e881cd137f900d8903f02a07f87 Mon Sep 17 00:00:00 2001 From: Ciprian Hacman Date: Wed, 3 Jun 2020 07:46:30 +0300 Subject: [PATCH] Update docs referencing the push-aws-run target --- docs/development/adding_a_feature.md | 2 +- docs/development/building.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/development/adding_a_feature.md b/docs/development/adding_a_feature.md index 6360bf7aa0..dc2f225422 100644 --- a/docs/development/adding_a_feature.md +++ b/docs/development/adding_a_feature.md @@ -226,7 +226,7 @@ You can `make` and run `kops` locally. But `nodeup` is pulled from an S3 bucket To rapidly test a nodeup change, you can build it, scp it to a running machine, and run it over SSH with the output viewable locally: -`make push-aws-run TARGET=admin@` +`make push-aws-run-amd64 TARGET=admin@` For more complete testing though, you will likely want to do a private build of diff --git a/docs/development/building.md b/docs/development/building.md index 840f6ff2e0..91b2f359d1 100644 --- a/docs/development/building.md +++ b/docs/development/building.md @@ -25,7 +25,7 @@ make ## Cross Compiling -Cross compiling for things like `nodeup` are now done automatically via `make nodeup`. `make push-aws-run TARGET=admin@$TARGET` will automatically choose the linux amd64 build from your `.build` directory. +Cross compiling for things like `nodeup` are now done automatically via `make nodeup`. `make push-aws-run-amd64 TARGET=admin@$TARGET` will automatically choose the linux amd64 build from your `.build` directory. ## Debugging