RexOps / RexOps/Rex

Can private_key be used as a property for a server?

Open
#1,286 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Perl
Stars
737
Forks
214
PR merge metrics
No merged PRs in 30d

Description

The documentation on configuring a server is thin.

I have this in Rexfile:

group "lightsails", "ilwu_big" => { user => 'my_user', private_key => '/path/to/key.pem' };

task 'uptime', 'ilwu_big', sub {
  say run 'uptime';
};

However, authentication fails. If I add the following above the task, however:

private_key '/path/to/key.pem';

The task runs.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Rexfile examples for the group server configuration and the private_key entry point, then compare the group property with the standalone private_key call used by the uptime task. Confirm whether both forms are intended to authenticate the server; done means the supported behavior is clarified and the documentation or configuration handling is made consistent.

Written by the indexing model from the issue text.

Assessment

Tech stack
perl
Domain
devops, infrastructure
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.