Name confusion between the Waypoint Exec command and the Waypoint Exec plugin

I would like to crowd-source ideas from the community about how to better disambiguate the Waypoint exec function (exec into a running container/app) from the Waypoint Exec plugin.

The Exec plugin is used as a type of escape hatch to be able to use Waypoint with existing app workflows and still have the benefit of the Waypoint Entrypoint functions.

waypoint exec (run at the command line), is used to open a shell into a running application that you have deployed with Waypoint.

These are clearly very different functions, and I find it confusing that we use the same name both places. It does not make sense to rename the command/function, so it has to be the plugin. :slight_smile:

Potential new names for the plugin (please recommend others):

  • external
  • remote
  • out
  • ??

Before I open a GitHub issue, I want to see what others think.

I have filed the following Issue - Rename the Exec plugin to eliminate confusion with the ‘waypoint exec’ command · Issue #1079 · hashicorp/waypoint (

The current proposal is to change the name of the exec plugin to local-exec.

@krantzinator and @briancain, what do you think?

I left a comment on the GH issue! I think it makes sense to keep the discussion there for now, so I won’t copy over what I said :grinning_face_with_smiling_eyes:

1 Like

Thanks! I will move back over there. :slight_smile: