https://pulumi.com logo
#automation-api
Title
# automation-api
a

alert-processor-41605

02/23/2021, 9:21 PM
Loving the automation API! I have a quick question about a new issue that's come up with the automation api. When I run "up" on a stack, I get an error
unknown flag: --page-size
after the up runs. Up is successful, but this error is thrown whent he history is getting fetched. This happened locally and running
brew upgrade pulumi
fixed the problem. When I'm running in my CI environment (Github Actions), however, I do not know how to resolve it as I don't have a specific version of pulumi running in the action. Any thoughts on how to resolve this? I will put the full error in a thread below.
Copy code
CommandError: code: 1
 stdout: 
 stderr: Error: unknown flag: --page-size
Usage:
  pulumi history [flags]

ERROR: Something went wrong in @nrwl/run-commands - Command failed: node ./apps/pulumi/projects/infrastructure/automation/up.js
Aliases:
  history, hist

Flags:
  -h, --help           help for history
  -j, --json           Emit output as JSON
      --show-secrets   Show secret values when listing config instead of displaying blinded values
  -s, --stack string   Choose a stack other than the currently selected one

Global Flags:
      --color string                 Colorize output. Choices are: always, never, raw, auto (default "auto")
  -C, --cwd string                   Run pulumi as if it had been started in another directory
      --disable-integrity-checking   Disable integrity checking of checkpoint files
  -e, --emoji                        Enable emojis in the output
      --logflow                      Flow log settings to child processes (like plugins)
      --logtostderr                  Log to stderr instead of to files
      --non-interactive              Disable interactive mode for all commands
      --profiling string             Emit CPU and memory profiles and an execution trace to '[filename].[pid].{cpu,mem,trace}', respectively
      --tracing file:                Emit tracing to the specified endpoint. Use the file: scheme to write tracing data to a local file
  -v, --verbose int                  Enable verbose logging (e.g., v=3); anything >3 is very verbose

An error occurred: unknown flag: --page-size

 err?: 

    at Object.createCommandError (/home/runner/work/core/core/node_modules/@pulumi/pulumi/x/automation/errors.js:71:17)
    at ChildProcess.<anonymous> (/home/runner/work/core/core/node_modules/@pulumi/pulumi/x/automation/cmd.js:63:40)
    at ChildProcess.emit (events.js:314:20)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:276:12) {
  commandResult: CommandResult {
    stdout: '',
    stderr: 'Error: unknown flag: --page-size\n' +
      'Usage:\n' +
      '  pulumi history [flags]\n' +
      '\n' +
      'Aliases:\n' +
      '  history, hist\n' +
      '\n' +
      'Flags:\n' +
      '  -h, --help           help for history\n' +
      '  -j, --json           Emit output as JSON\n' +
      '      --show-secrets   Show secret values when listing config instead of displaying blinded values\n' +
      '  -s, --stack string   Choose a stack other than the currently selected one\n' +
      '\n' +
      'Global Flags:\n' +
      '      --color string                 Colorize output. Choices are: always, never, raw, auto (default "auto")\n' +
      '  -C, --cwd string                   Run pulumi as if it had been started in another directory\n' +
      '      --disable-integrity-checking   Disable integrity checking of checkpoint files\n' +
      '  -e, --emoji                        Enable emojis in the output\n' +
      '      --logflow                      Flow log settings to child processes (like plugins)\n' +
      '      --logtostderr                  Log to stderr instead of to files\n' +
      '      --non-interactive              Disable interactive mode for all commands\n' +
      "      --profiling string             Emit CPU and memory profiles and an execution trace to '[filename].[pid].{cpu,mem,trace}', respectively\n" +
      '      --tracing file:                Emit tracing to the specified endpoint. Use the file: scheme to write tracing data to a local file\n' +
      '  -v, --verbose int                  Enable verbose logging (e.g., v=3); anything >3 is very verbose\n' +
      '\n' +
      'An error occurred: unknown flag: --page-size\n',
    code: 1,
    err: undefined
  }
}
error Command failed with exit code 1.
info Visit <https://yarnpkg.com/en/docs/cli/run> for documentation about this command.
Error: Process completed with exit code 1.
Seeing now that GitHub actions has
2.20.0
installed on it by default. Gonna downgrade my pulumi node package and try it on version
2.20.0
https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu2004-README.md
b

broad-dog-22463

02/23/2021, 9:34 PM
Hi @alert-processor-41605 You can use https://github.com/pulumi/action-install-pulumi-cli in your GHA runner to upgrade to latest
a

alert-processor-41605

02/23/2021, 9:35 PM
This looks perfect! Thank you 🙂