Skip to content

feat: add scenario info#165

Merged
jrvb-rl merged 1 commit intojrvb/add-logs-commandfrom
jrvb/add-scenario-info
Mar 10, 2026
Merged

feat: add scenario info#165
jrvb-rl merged 1 commit intojrvb/add-logs-commandfrom
jrvb/add-scenario-info

Conversation

@jrvb-rl
Copy link
Copy Markdown
Contributor

@jrvb-rl jrvb-rl commented Mar 10, 2026

Add an rli non-interactive command to fetch, format and print scenario info

@jrvb-rl jrvb-rl changed the base branch from main to jrvb/add-logs-command March 10, 2026 08:35
@jrvb-rl jrvb-rl requested review from james-rl and ross-rl March 10, 2026 08:36
Copy link
Copy Markdown
Contributor

@james-rl james-rl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me.

As a general usability consideration that's not specifically related to this PR: I think it's always beneficial to explicitly define the expected working directory.

Comment on lines +91 to +97
if (env) {
console.log();
console.log(chalk.bold("Environment:"));
if (env.blueprint_id) console.log(` blueprint: ${env.blueprint_id}`);
if (env.snapshot_id) console.log(` snapshot: ${env.snapshot_id}`);
if (env.working_directory)
console.log(` working_directory: ${env.working_directory}`);
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This isn't an issue in this code, but I'm coming to the opinion that we should always set an explicit working directory. Not specifying it leads to potentially confusing default values.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah - in general doing a better job sanitizing working dir behavior would make all of this more robust...

@jrvb-rl jrvb-rl merged commit dd376b8 into jrvb/add-logs-command Mar 10, 2026
13 of 15 checks passed
@jrvb-rl jrvb-rl deleted the jrvb/add-scenario-info branch March 10, 2026 18:43
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

Successfully merging this pull request may close these issues.

2 participants