Skip to content

feature: send force parameter to deployment api#10

Open
vitormorales wants to merge 2 commits intomainfrom
feature/pass-force-parameter-to-api
Open

feature: send force parameter to deployment api#10
vitormorales wants to merge 2 commits intomainfrom
feature/pass-force-parameter-to-api

Conversation

@vitormorales
Copy link
Copy Markdown
Member

@vitormorales vitormorales commented Mar 31, 2026

Summary

  • Forward the --force flag value to the formspree API call, so the API is aware when a forced deployment is requested.
  • This is needed updating HMAC secret using the CLI.
    If a key already exists and the user wants to update it, should use this flag.
  • Default is false

@vitormorales vitormorales changed the title feature: passes force parameter to deployment api feature: send force parameter to deployment api Mar 31, 2026
@colevscode
Copy link
Copy Markdown
Member

Please provide more descriptive PR comment.

Also this isn't accurate anymore:


  yargs.option('force', {
    alias: 'f',
    describe: 'Skip verifying that secrets reference environment variables',
    type: 'boolean',
    default: false
  });

@vitormorales
Copy link
Copy Markdown
Member Author

vitormorales commented Apr 1, 2026

Please provide more descriptive PR comment.

Also this isn't accurate anymore:


  yargs.option('force', {
    alias: 'f',
    describe: 'Skip verifying that secrets reference environment variables',
    type: 'boolean',
    default: false
  });

Sorry for that. Updated the description either in code and PR. I checked and we still skip any invalidKey when --force is used.

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