https://github.com/memes/f5-nginxaas-for-google-cloud-examples
Some deployment examples for F5 NGINXaaS for Google Cloud
https://github.com/memes/f5-nginxaas-for-google-cloud-examples
Last synced: 4 months ago
JSON representation
Some deployment examples for F5 NGINXaaS for Google Cloud
- Host: GitHub
- URL: https://github.com/memes/f5-nginxaas-for-google-cloud-examples
- Owner: memes
- License: apache-2.0
- Created: 2025-09-15T18:39:06.000Z (10 months ago)
- Default Branch: main
- Last Pushed: 2025-09-30T19:02:15.000Z (10 months ago)
- Last Synced: 2025-09-30T21:06:47.211Z (10 months ago)
- Language: HCL
- Homepage:
- Size: 86.9 KB
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
- Codeowners: CODEOWNERS
Awesome Lists containing this project
README
# F5 Google demo bootstrap template for Google Cloud


[](CODE_OF_CONDUCT.md)
This repository contains common settings and actions that are typical to my demo projects and is designed to be used
with the [bootstrap](https://github.com/memes/terraform-google-f5-demo-bootstrap) module as a starting point for
automated deployments.
## Setup
> NOTE: TODOs are sprinkled in the files and can be used to find where changes
> may be necessary.
1. Use as a template when creating a new GitHub repo, or copy the contents into
a bare-repo directory.
2. Update `.pre-commit-config.yml` to add/remove plugins as necessary.
3. Modify README.md and CONTRIBUTING.md, change LICENSE as needed.
4. Review GitHub PR and issue templates.
5. If using `release-please` action, make these changes:
1. In GitHub Settings:
* _Settings_ > _Actions_ > _General_ > _Allow GitHub Actions to create and approve pull requests_ is checked
* _Settings_ > _Secrets and Variables_ > _Actions_, and add `RELEASE_PLEASE_TOKEN` with PAT as a _Repository Secret_
2. Modify [release-please action](.github/workflows/release-please.yml) to enable it
3. Modify [release-please-config.json](release-please-config.json)] as needed
4. Reset [.release-please-manifest.json](.release-please-manifest.json) to an empty file or starting version for package(s).
6. Remove all [CHANGELOG](CHANGELOG.md) entries.
7. Modify [pyproject.toml](pyproject.toml) name and dependencies, as needed, delete [uv.lock](uv.lock) and regenerate.
8. Modify [devcontainer](.devcontainer/devcontainer.json) name, etc., as needed, test.
9. Commit changes.