| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
The content has been merged with fcuny.net - I can keep everything in
one site.
|
| |
|
|
|
| |
All the repositories should be on GitHub now, and archived if they are
not relevant anymore.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
We first need to create a repository before we can create the default
branch. For the default branch to be set, we also need the repository to
contain a commit, which is achieved with the `auto_init' attribute.
We can always push with `--force' to overwrite that initial commit when
doing the migration.
|
| |
|
|
|
|
|
| |
It's been moved to its own repository at
https://github.com/fcuny/mpd-stats
Update the list of repositories managed by terraform.
|
| |
|
|
|
| |
While not great, this is the default workflow on GitHub. It's also what
allows my `git-broom` CLI to work with branches on GitHub.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
From now on we should always be using 'main'. If a project requires
'master', it will need to be set explicitly.
|
| |
|
|
|
|
| |
Move all the repositories in a YAML file, instead of declaring each
repository. This will simplify the management as I'll be introducing
more resources to manage my repositories.
|
| | |
|
| |
|
|
| |
It's back at https://github.com/fcuny/govanity
|
| | |
|
| | |
|
| |
|
|
|
| |
Don't do all of these actions together, instead provide helpers for both
init, plan, and apply.
|
| | |
|
| |
|
|
|
|
| |
Import current GitHub repositories into terraform. This should be the
main way (going forward) to interact with GitHub to create / manage the
repositories and ensuring I'm consistent in the ways I want to use it.
|
| |
|
|
|
|
|
| |
Change-Id: Id11ad998c30d6e863ab3b43552b9fe248a0d6c7f
Reviewed-on: https://cl.fcuny.net/c/world/+/716
Tested-by: CI
Reviewed-by: Franck Cuny <franck@fcuny.net>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This terraform configuration is to create the buckets that I'm using for
various buckets. Doing this through the UI is difficult, as there are
too many options, it's easy to have different buckets with different
settings when I need them to be identical, no way to review what the
change is going to look like, etc.
Change-Id: I8ee15939559e7632e2df9d17cfaec75d756930b6
Reviewed-on: https://cl.fcuny.net/c/world/+/713
Tested-by: CI
Reviewed-by: Franck Cuny <franck@fcuny.net>
|
| |
|
|
|
|
|
| |
Change-Id: Ifb970bc6835fbc0de1943349739524331b6dba76
Reviewed-on: https://cl.fcuny.net/c/world/+/712
Reviewed-by: Franck Cuny <franck@fcuny.net>
Tested-by: CI
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since I'm using terraform for a few things, I want to store the state in
a GCP bucket. This script takes care of creating the bucket, creating
the service account for terraform, setting the roles, and enabling
impersonation.
The script is (or at least is intended) to be idempotent. If a new
project is created, running will update only what is needed.
Change-Id: Ie92703be6d17749dc76dabcf9e73e7b274e8d2ac
Reviewed-on: https://cl.fcuny.net/c/world/+/711
Reviewed-by: Franck Cuny <franck@fcuny.net>
Tested-by: CI
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of using a key for the terraform service account, use
delegation. This simplifies a bit the setup:
- no need to have a local key
- principle of least privilege
- no need to setup some environment variables
Update the documentation in case something goes wrong in the future.
Change-Id: I430bdf6816419da35ae8a36cec55ce56491b985c
Reviewed-on: https://cl.fcuny.net/c/world/+/710
Tested-by: CI
Reviewed-by: Franck Cuny <franck@fcuny.net>
|
| |
|
|
|
|
|
| |
Change-Id: I63fc8fd81679457f7dbeafc2bd10c0eded0de991
Reviewed-on: https://cl.fcuny.net/c/world/+/707
Tested-by: CI
Reviewed-by: Franck Cuny <franck@fcuny.net>
|
| |
|
|
|
|
|
|
|
|
|
| |
This is the pipeline that is executed when a new build starts. It wait
for all the steps to be completed, and if one of them fail, the build is
marked as failed.
Change-Id: I1eb22b27749944de78d44e49586a1db1fe07b460
Reviewed-on: https://cl.fcuny.net/c/world/+/706
Tested-by: CI
Reviewed-by: Franck Cuny <franck@fcuny.net>
|
| |
|
|
|
|
|
|
|
|
| |
Since I have configured the pre-commit hooks, I can use them instead of
my custom scripts: less things to maintain and easier to read output.
Change-Id: Ic833ec88ed9fbcbe52b1b1680f978da3a5a08b31
Reviewed-on: https://cl.fcuny.net/c/world/+/681
Tested-by: CI
Reviewed-by: Franck Cuny <franck@fcuny.net>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
I can now run `nix run .#ci.shellcheck` to validate the shell scripts
with shellcheck in the repository.
The pipeline in buildKite will need to be updated.
Change-Id: Ia52ede86adfa58c9615b0f9e290ef5d5b8adb303
Reviewed-on: https://cl.fcuny.net/c/world/+/409
Tested-by: CI
Reviewed-by: Franck Cuny <franck@fcuny.net>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The script uses shellcheck to validates that the shell scripts are
correct.
This is not used by anything yet.
Change-Id: Ia96b132143fa0824eaf23420a72e5b518d618250
Reviewed-on: https://cl.fcuny.net/c/world/+/407
Tested-by: CI
Reviewed-by: Franck Cuny <franck@fcuny.net>
|
|
|
Add a script for CI to check that all the files are formatted correctly.
This is done by using `treefmt' with a configuration for go and nix
files (for now).
Running `nix run .#ci.fmt' in the repository will check all the files,
and fail if there's any problems. It will not modify any files.
The pipeline in builKite needs to be updated to run that command.
Change-Id: Iec91163f1ab56ceb0cfff6db8f8ce93367ebeefe
Reviewed-on: https://cl.fcuny.net/c/world/+/403
Tested-by: CI
Reviewed-by: Franck Cuny <franck@fcuny.net>
|
