docs: Remove AWS deployment and update CLI documentation#8
Conversation
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| runs-on: ubuntu-latest | ||
| steps: | ||
| - uses: actions/checkout@v4 | ||
| - name: Publish GitHub Release | ||
| uses: softprops/action-gh-release@v2 | ||
| with: | ||
| tag_name: ${{ github.ref_name }} | ||
| name: ${{ github.ref_name }} | ||
| generate_release_notes: true | ||
| draft: false | ||
| prerelease: false | ||
| env: | ||
| GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} No newline at end of file |
Check warning
Code scanning / CodeQL
Workflow does not contain permissions Medium
Show autofix suggestion
Hide autofix suggestion
Copilot Autofix
AI 3 days ago
In general, the fix is to explicitly declare a permissions block, either at the workflow root (applies to all jobs) or at the individual job level, granting only the minimum scopes required. For a release-creation workflow using softprops/action-gh-release, the job needs to write releases (and typically contents), so we should grant contents: write (and optionally a narrower contents: write without other write scopes). We do not need broad write access to issues, pull requests, etc., so we should avoid those unless the workflow actually uses them.
The best targeted fix here is to add a permissions block under the create job (right below runs-on: ubuntu-latest) specifying minimal necessary scopes. According to GitHub’s permission model, to create a release we need contents: write. We can therefore add:
permissions:
contents: writeimmediately under runs-on: ubuntu-latest. This keeps existing functionality intact while constraining GITHUB_TOKEN to only what the job requires. No additional imports or libraries are involved, since this is just a YAML workflow configuration change within .github/workflows/create-release.yml.
| @@ -7,6 +7,8 @@ | ||
| jobs: | ||
| create: | ||
| runs-on: ubuntu-latest | ||
| permissions: | ||
| contents: write | ||
| steps: | ||
| - uses: actions/checkout@v4 | ||
| - name: Publish GitHub Release |
1 participant
Summary
This PR removes all AWS-specific deployment content and updates the documentation to focus on CLI-based installation as the primary method.
Changes Made
Priority 1: Critical Changes
docs/deploying/deploy-to-aws.md(188 lines of AWS-specific content)docs/getting-started/install/install-with-cli.md- New primary installation guidedocs/introduction.md- Removed AWS section, added CLI quick startdocs/quick-start.md- Complete rewrite focusing on CLI installationdocs/extensions/fleetbase-cli.md- Added all new commands and developer account guidesPriority 2: Important Changes
docs/deploying/deploy-cloud.md- Removed AWS section, reordered providers (DigitalOcean first)docs/deploying/deploy-on-premise.md- Added CLI as recommended methodPriority 3: Cleanup
New Features
CLI Installation Guide
Developer Account Documentation
Updated Commands
flb install-fleetbase- Install Fleetbase with Dockerflb register- Register developer accountflb verify- Verify email addressflb resend-verification- Resend verification codeflb generate-token- Generate/regenerate registry tokenflb set-auth- Set registry authentication tokenImpact
Testing
Related Issues
Closes #[issue-number] (if applicable)
Note: This PR makes CLI-based installation the default and recommended method for all users, while maintaining manual Docker and source installation options for advanced users.