Skip to content

Commit

Permalink
chore: rename after org change (#853)
Browse files Browse the repository at this point in the history
Various changes made after the GitHub org name changed. The changes
include Go packagae names/import, contaienr images names etc.

Signed-off-by: Richard Case <[email protected]>
  • Loading branch information
richardcase authored Jul 9, 2024
1 parent 8fcd8d3 commit b50da53
Show file tree
Hide file tree
Showing 153 changed files with 960 additions and 937 deletions.
10 changes: 3 additions & 7 deletions .github/ISSUE_TEMPLATE/bug_report.md
Original file line number Diff line number Diff line change
@@ -1,9 +1,9 @@
---
name: Bug report
about: Tell us about a problem you are experiencing
title: ''
title: ""
labels: kind/bug
assignees: ''
assignees: ""
---

<!--
Expand All @@ -13,23 +13,19 @@ Before creating a new request for help, please search existing issues to see if
If there is a similar feature request please up-vote it and/or add your comments to it instead
For more information on how to request help on flintlock, please refer to our community docs.
https://github.com/weaveworks-liquidmetal/flintlock/blob/main/CONTRIBUTING.md#opening-issues
https://github.com/liquidmetal-dev/flintlock/blob/main/CONTRIBUTING.md#opening-issues
-->

**What happened:**
[A clear and concise description of what the bug is.]


**What did you expect to happen:**


**How to reproduce it:**


**Anything else you would like to add:**
[Miscellaneous information that will assist in solving the issue.]


**Environment:**

- flintlock version:
Expand Down
6 changes: 3 additions & 3 deletions .github/ISSUE_TEMPLATE/feature_request.md
Original file line number Diff line number Diff line change
@@ -1,9 +1,9 @@
---
name: Feature enhancement request
about: Suggest an idea for flintlock
title: ''
title: ""
labels: kind/feature
assigness: ''
assigness: ""
---

<!--
Expand All @@ -13,7 +13,7 @@ Before creating a new feature request, please search existing issues to see if y
If there is a similar feature request please up-vote it and/or add your comments to it instead
For more information on how to request help on flintlock, please refer to our community docs.
https://github.com/weaveworks-liquidmetal/flintlock/blob/main/CONTRIBUTING.md#opening-issues
https://github.com/liquidmetal-dev/flintlock/blob/main/CONTRIBUTING.md#opening-issues
-->

**Describe the solution you'd like:**
Expand Down
4 changes: 2 additions & 2 deletions .github/workflows/dependabot_bundler.yml
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ jobs:
- name: Setup Go
uses: actions/setup-go@v3
with:
go-version-file: '${{ github.workspace }}/go.mod'
go-version-file: "${{ github.workspace }}/go.mod"
- name: Cache go-build and mod
uses: actions/cache@v2
with:
Expand All @@ -34,7 +34,7 @@ jobs:
run: |
dependabot-bundler \
--token ${{ secrets.GITHUB_TOKEN }} \
--owner weaveworks-liquidmetal \
--owner liquidmetal-dev \
--repo flintlock \
--labels 'area/dependency,kind/cleanup,user-signing-required' \
--pr-title 'chore(deps): Bundle dependabot pull requests'
12 changes: 6 additions & 6 deletions .github/workflows/deploy-docs.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -14,23 +14,23 @@ jobs:
- uses: actions/checkout@v1
- uses: actions/setup-node@v1
with:
node-version: '16.x'
node-version: "16.x"
- uses: actions/setup-go@v3
with:
go-version-file: '${{ github.workspace }}/go.mod'
go-version-file: "${{ github.workspace }}/go.mod"
- name: Build docs
run: make docs-build
release:
if: ${{ github.event_name != 'pull_request' && github.repository_owner == 'weaveworks-liquidmetal' }}
if: ${{ github.event_name != 'pull_request' && github.repository_owner == 'liquidmetal-dev' }}
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v1
- uses: actions/setup-node@v1
with:
node-version: '16.x'
node-version: "16.x"
- uses: actions/setup-go@v3
with:
go-version-file: '${{ github.workspace }}/go.mod'
go-version-file: "${{ github.workspace }}/go.mod"
- uses: webfactory/[email protected]
with:
ssh-private-key: ${{ secrets.BOT_DEPLOY_KEY }}
Expand All @@ -41,5 +41,5 @@ jobs:
DEPLOYMENT_BRANCH: gh-pages
run: |
git config --global user.email "[email protected]"
git config --global user.name "weaveworks-docs-bot"
git config --global user.name "liquidmetal-docs-bot"
make docs-deploy
130 changes: 65 additions & 65 deletions .github/workflows/fork.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -3,84 +3,84 @@ name: bump firecracker
on:
workflow_dispatch: {}
schedule:
- cron: 0 0 * * 1
- cron: 0 0 * * 1

jobs:
update:
runs-on: ubuntu-latest
permissions:
issues: write
steps:
- name: Checkout
uses: actions/checkout@v2
with:
ssh-key: ${{ secrets.WEAVEWORKSBOT_TOKEN }}
fetch-depth: 0
- name: Bump firecracker?
run: |
new_version=$(./hack/scripts/bump_firecracker.sh)
if [[ "$new_version" == "" ]]; then
echo "No new Firecracker release. Nothing to do. (this is not an error, no worries.)"
fi
- name: Checkout
uses: actions/checkout@v2
with:
ssh-key: ${{ secrets.LIQUIDMETALBOT_TOKEN }}
fetch-depth: 0
- name: Bump firecracker?
run: |
new_version=$(./hack/scripts/bump_firecracker.sh)
if [[ "$new_version" == "" ]]; then
echo "No new Firecracker release. Nothing to do. (this is not an error, no worries.)"
fi
echo 'NEW_VERSION<<EOF' >> $GITHUB_ENV
echo "${new_version}" >> $GITHUB_ENV
echo 'EOF' >> $GITHUB_ENV
- name: Create Issue
if: ${{ env.NEW_VERSION != '' }}
uses: imjohnbo/issue-bot@v3
id: issue
with:
title: 'Bump firecracker version to ${{ env.NEW_VERSION }}'
pinned: false
close-previous: true
assignees: "Callisto13, yitsushi, Skarlso"
rotate-assignees: true
body: |-
This is an automatically generated Issue to release a new version of
Firecracker on our fork.
There are some manual steps to get new releases of our fork
branch published.
This Issue is to track those manual steps.
echo 'NEW_VERSION<<EOF' >> $GITHUB_ENV
echo "${new_version}" >> $GITHUB_ENV
echo 'EOF' >> $GITHUB_ENV
- name: Create Issue
if: ${{ env.NEW_VERSION != '' }}
uses: imjohnbo/issue-bot@v3
id: issue
with:
title: "Bump firecracker version to ${{ env.NEW_VERSION }}"
pinned: false
close-previous: true
assignees: "Callisto13, yitsushi, Skarlso"
rotate-assignees: true
body: |-
This is an automatically generated Issue to release a new version of
Firecracker on our fork.
There are some manual steps to get new releases of our fork
branch published.
This Issue is to track those manual steps.
**Note that for now we are mirroring firecracker's releases of v1.1.x, v1.2.x and v1.3.x versions**.
**Note that for now we are mirroring firecracker's releases of v1.1.x, v1.2.x and v1.3.x versions**.
To complete work on this Issue:
- [ ] Clone [our fork](https://github.com/weaveworks/firecracker) (if you do not have it already).
- [ ] Add the upstream as a remote: `git add remote up https://github.com/firecracker-microvm/firecracker`
- [ ] Fetch all branches and tags: `git fetch && git fetch --tags`
- [ ] Check out to the relevant `macvtap` version branch. `feature/macvtap` for a new `v1.2.x` release, `feature/macvtapv11x` for a new `v1.1.x` release.
- [ ] Update the feature branch. `git rebase firecracker-v1.3` for a `v1.3.x` release `git rebase firecracker-v1.2` for a `v1.2.x` release, etc. etc.
- [ ] Resolve any merge conflicts if necessary. (There will be merge conflicts.)
- [ ] Add any code if necessary. (This will gradually become more necessary, because the older this feature branch gets, the more the code around it upstream will change.)
- [ ] Make sure it builds. (`tools/devtool build`)
- [ ] Push the updated firecracker 'feature/macvtap' (or `firecracker/macvtapv12`, etc) fork branch.
- [ ] Create a new tag on the updated firecracker fork branch: `git tag -s ${{ env.NEW_VERSION}}-macvtap -m ${{ env.NEW_VERSION }}-macvtap`.
- [ ] Push the tag to the fork: `git push <remote> ${{ env.NEW_VERSION }}-macvtap` (A new [release](https://github.com/weaveworks/firecracker/releases) will be created.)
- [ ] In this repo, trigger the `nightly_e2e` workflow
- [ ] Once the tests have passed you can close the Issue, if the tests fail, either fix them or unrelease the version
To complete work on this Issue:
- [ ] Clone [our fork](https://github.com/liquidmetal-dev/firecracker) (if you do not have it already).
- [ ] Add the upstream as a remote: `git add remote up https://github.com/firecracker-microvm/firecracker`
- [ ] Fetch all branches and tags: `git fetch && git fetch --tags`
- [ ] Check out to the relevant `macvtap` version branch. `feature/macvtap` for a new `v1.2.x` release, `feature/macvtapv11x` for a new `v1.1.x` release.
- [ ] Update the feature branch. `git rebase firecracker-v1.3` for a `v1.3.x` release `git rebase firecracker-v1.2` for a `v1.2.x` release, etc. etc.
- [ ] Resolve any merge conflicts if necessary. (There will be merge conflicts.)
- [ ] Add any code if necessary. (This will gradually become more necessary, because the older this feature branch gets, the more the code around it upstream will change.)
- [ ] Make sure it builds. (`tools/devtool build`)
- [ ] Push the updated firecracker 'feature/macvtap' (or `firecracker/macvtapv12`, etc) fork branch.
- [ ] Create a new tag on the updated firecracker fork branch: `git tag -s ${{ env.NEW_VERSION}}-macvtap -m ${{ env.NEW_VERSION }}-macvtap`.
- [ ] Push the tag to the fork: `git push <remote> ${{ env.NEW_VERSION }}-macvtap` (A new [release](https://github.com/liquidmetal-dev/firecracker/releases) will be created.)
- [ ] In this repo, trigger the `nightly_e2e` workflow
- [ ] Once the tests have passed you can close the Issue, if the tests fail, either fix them or unrelease the version
Auto-generated by [issue-bot](https://github.com/imjohnbo/issue-bot).
labels: "area/firecracker, area/dependency, kind/feature, priority/critical-urgent"
- name: Notify slack on creation success
if: ${{ success() && env.NEW_VERSION != '' }}
uses: actions-ecosystem/action-slack-notifier@fc778468d09c43a6f4d1b8cccaca59766656996a
with:
slack_token: ${{ secrets.SLACK_TOKEN }}
message: "There is a new version of Firecracker, complete the todo list here: <https://github.com/weaveworks-liquidmetal/flintlock/issues/${{ steps.issue.outputs.issue-number }}|#${{ steps.issue.outputs.issue-number }}>."
channel: liquid-metal-dev
color: green
verbose: false
Auto-generated by [issue-bot](https://github.com/imjohnbo/issue-bot).
labels: "area/firecracker, area/dependency, kind/feature, priority/critical-urgent"
- name: Notify slack on creation success
if: ${{ success() && env.NEW_VERSION != '' }}
uses: actions-ecosystem/action-slack-notifier@fc778468d09c43a6f4d1b8cccaca59766656996a
with:
slack_token: ${{ secrets.SLACK_TOKEN }}
message: "There is a new version of Firecracker, complete the todo list here: <https://github.com/liquidmetal-dev/flintlock/issues/${{ steps.issue.outputs.issue-number }}|#${{ steps.issue.outputs.issue-number }}>."
channel: liquid-metal-dev
color: green
verbose: false
notify:
needs: [update]
if: ${{ failure() }}
runs-on: ubuntu-latest
steps:
- name: Notify slack on failure
uses: actions-ecosystem/action-slack-notifier@fc778468d09c43a6f4d1b8cccaca59766656996a
with:
slack_token: ${{ secrets.SLACK_TOKEN }}
message: "There is a new firecracker version, but the 'Bump Firecracker' issue failed :sad-parrot: <https://github.com/${{ github.repository }}/actions/runs/${{ github.run_id }}|Click here>."
channel: liquid-metal-dev
color: red
verbose: false
- name: Notify slack on failure
uses: actions-ecosystem/action-slack-notifier@fc778468d09c43a6f4d1b8cccaca59766656996a
with:
slack_token: ${{ secrets.SLACK_TOKEN }}
message: "There is a new firecracker version, but the 'Bump Firecracker' issue failed :sad-parrot: <https://github.com/${{ github.repository }}/actions/runs/${{ github.run_id }}|Click here>."
channel: liquid-metal-dev
color: red
verbose: false
82 changes: 41 additions & 41 deletions .github/workflows/nightly_e2e.yml
Original file line number Diff line number Diff line change
Expand Up @@ -8,53 +8,53 @@ on:
jobs:
e2e:
runs-on: ubuntu-latest
if: ${{ github.event_name != 'pull_request' && github.repository_owner == 'weaveworks-liquidmetal' }}
if: ${{ github.event_name != 'pull_request' && github.repository_owner == 'liquidmetal-dev' }}
env:
PROJECT_NAME: "flintlock_nightly_e2e"
name: e2e tests
steps:
- uses: actions/checkout@v2
- uses: actions/checkout@v2

- name: Get branch name
id: branch-name
uses: tj-actions/branch-names@v5
- name: Get branch name
id: branch-name
uses: tj-actions/branch-names@v5

- name: Run tests
env:
METAL_AUTH_TOKEN: ${{ secrets.METAL_AUTH_TOKEN }}
run: |
pip3 install -r test/tools/requirements.txt
cat <<'EOF' >> e2e-config.yaml
---
org_id: ${{ secrets.EQUINIX_ORG_ID }}
project_name: ${{ env.PROJECT_NAME }}
repo:
branch: ${{ steps.branch-name.outputs.current_branch }}
EOF
test/tools/run.py run-e2e -c e2e-config.yaml
- name: Run tests
env:
METAL_AUTH_TOKEN: ${{ secrets.METAL_AUTH_TOKEN }}
run: |
pip3 install -r test/tools/requirements.txt
cat <<'EOF' >> e2e-config.yaml
---
org_id: ${{ secrets.EQUINIX_ORG_ID }}
project_name: ${{ env.PROJECT_NAME }}
repo:
branch: ${{ steps.branch-name.outputs.current_branch }}
EOF
test/tools/run.py run-e2e -c e2e-config.yaml
- name: Notify slack on failure
uses: actions-ecosystem/action-slack-notifier@fc778468d09c43a6f4d1b8cccaca59766656996a
if: ${{ failure() }}
with:
slack_token: ${{ secrets.SLACK_TOKEN }}
message: "A flintlock integration test run failed :sad-parrot: <https://github.com/${{ github.repository }}/actions/runs/${{ github.run_id }}|Click here> and weep."
channel: liquid-metal-dev
color: red
verbose: false
- name: Notify slack on failure
uses: actions-ecosystem/action-slack-notifier@fc778468d09c43a6f4d1b8cccaca59766656996a
if: ${{ failure() }}
with:
slack_token: ${{ secrets.SLACK_TOKEN }}
message: "A flintlock integration test run failed :sad-parrot: <https://github.com/${{ github.repository }}/actions/runs/${{ github.run_id }}|Click here> and weep."
channel: liquid-metal-dev
color: red
verbose: false

- name: Notify slack on success
uses: actions-ecosystem/action-slack-notifier@fc778468d09c43a6f4d1b8cccaca59766656996a
if: ${{ success() }}
with:
slack_token: ${{ secrets.SLACK_TOKEN }}
message: "A flintlock integration test run succeeded :party-gopher:"
channel: liquid-metal-dev
color: green
verbose: false
- name: Notify slack on success
uses: actions-ecosystem/action-slack-notifier@fc778468d09c43a6f4d1b8cccaca59766656996a
if: ${{ success() }}
with:
slack_token: ${{ secrets.SLACK_TOKEN }}
message: "A flintlock integration test run succeeded :party-gopher:"
channel: liquid-metal-dev
color: green
verbose: false

- name: Cleanup project
uses: weaveworks/metal-janitor-action@27a0594c5c92d85585b553fc0c5ef2a3de7bec95
with:
metal_auth_token: ${{ secrets.METAL_AUTH_TOKEN }}
project_names: ${{ env.PROJECT_NAME }}
- name: Cleanup project
uses: weaveworks/metal-janitor-action@27a0594c5c92d85585b553fc0c5ef2a3de7bec95
with:
metal_auth_token: ${{ secrets.METAL_AUTH_TOKEN }}
project_names: ${{ env.PROJECT_NAME }}
Loading

0 comments on commit b50da53

Please sign in to comment.