You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This ticket is most likely a "misunderstanding" ticket from a newbie but showing my working / thinking here so it may inform further enhancements / docs.
I've onboarded project1 and I automatically see 3 stages: dev, hardening and production. I didn't apply these stages and they don't exist in my Git repo so the operator is creating them automatically. To my (extremely limited) understanding of GitOps, this is against the paradigm as my repo should be the source of truth and thus I now have stages that do not appear in my repo.
I believe this is done because creating a keptn project without stages is not currently possible.
Perhaps I'm forced down this workflow because I'm using GitHub.com and modifying one file at a time rather than committing everything at once. Even so, this is, IMO, how most beginners would probably approach things.
Nevertheless, I create a .keptn/stage.yaml file (side note, is this name hardcoded? I'd like to call this stages.yaml instead):
So I decide to delete the shipyard.yaml file from the Git upstream, which is OK right, since gitops will see take the repo as the source of truth and regenerate the shipyard file.
Other Issues
I'm (seemingly randomly) getting the below even though project1 does exist:
This thread may lead to Keptn RFEs but the workflow that would work for me (and IMHO is the "most logical" esp. to a new user is):
1. Install operators
2. Create `instance.yaml`
3. Create `project.yaml` (this is an empty project without stages)
4. Create `stages.yaml` (creates an empty stage without sequences)
5. Create `sequences.yaml` with one or more sequences and tasks
6. Modify `stages.yaml` to link sequences
Up to step 4 would be the equivalent of the existing:
keptn create project project2 --shipyard=shipyard.yaml
Where shipyard.yaml:
At the moment you can't create create or remove stages, as keptn itself does not have this functionality (see keptn/enhancement-proposals#70). Therefore, initially, 3 Stages are created by default. This can also be overridden (base64-encode a shipyard file and paste this to spec.initialShipyard) of a KeptnProject.
Will take a look on the other errors and warnings later ...
This ticket is most likely a "misunderstanding" ticket from a newbie but showing my working / thinking here so it may inform further enhancements / docs.
I've onboarded
project1
and I automatically see 3 stages:dev
,hardening
andproduction
. I didn't apply these stages and they don't exist in my Git repo so the operator is creating them automatically. To my (extremely limited) understanding of GitOps, this is against the paradigm as my repo should be the source of truth and thus I now have stages that do not appear in my repo.I believe this is done because creating a keptn project without stages is not currently possible.
Perhaps I'm forced down this workflow because I'm using GitHub.com and modifying one file at a time rather than committing everything at once. Even so, this is, IMO, how most beginners would probably approach things.
Nevertheless, I create a
.keptn/stage.yaml
file (side note, is this name hardcoded? I'd like to call thisstages.yaml
instead):and my stage isn't created. In my Git upstream I see a
shipyard.yaml
file has been created for me so perhaps that is overriding the gitops operator:So I decide to delete the
shipyard.yaml
file from the Git upstream, which is OK right, since gitops will see take the repo as the source of truth and regenerate the shipyard file.Other Issues
I'm (seemingly randomly) getting the below even though
project1
does exist:This thread may lead to Keptn RFEs but the workflow that would work for me (and IMHO is the "most logical" esp. to a new user is):
Up to step 4 would be the equivalent of the existing:
apiVersion: "spec.keptn.sh/0.2.0"
kind: "Shipyard"
metadata:
name: "project2-shipyard"
spec:
stages:
- name: "stage1"
The text was updated successfully, but these errors were encountered: