Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Reorganise workflow yamls #267

Merged
merged 29 commits into from
Sep 12, 2024
Merged

chore: Reorganise workflow yamls #267

merged 29 commits into from
Sep 12, 2024

Conversation

stevekeay
Copy link
Contributor

@stevekeay stevekeay commented Sep 11, 2024

Replaces #262, moved the branch to this repo because CI was failing on the fork.

PUC-505 #closes #comment or is it [PUC-505]

@stevekeay stevekeay changed the title Reorganise workflow yamls feat: Reorganise workflow yamls Sep 11, 2024
Steve Keay added 25 commits September 11, 2024 12:40
We had a hierarchy of workflows that was not being fully utilised.  This
discards that structure in favour of the yaml file being organised by Kind and
then by name.

for i in `grep -lr "^kind: WorkflowTemplate"` ; do
  mv $i workflows/`cat "$i" | yq ".metadata.name"`.yaml
done
for i in `grep -lr "^kind: Sensor"` ; do
  mv $i sensors/`cat "$i" | yq ".metadata.name"`.yaml
done
etc
We don't use this structure any more.
These are separated out into folders by k8s namespace and then by "kind".

Kustomization is added to manage these
When CI runs on a fork it doesn't have permissions to push there
@stevekeay stevekeay force-pushed the reorganise-workflow-yamls branch 3 times, most recently from ea04eba to a8b300f Compare September 11, 2024 12:23
@cardoe cardoe changed the title feat: Reorganise workflow yamls chore: Reorganise workflow yamls Sep 11, 2024
Annotations should only be required on kind: WorkflowTemplate and kind:
CronWorkflowTemplate
@cardoe cardoe merged commit 4cd5b9e into main Sep 12, 2024
23 checks passed
@cardoe cardoe deleted the reorganise-workflow-yamls branch September 12, 2024 15:52
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