badhouseplants/badhouseplants-net-old
Archived
4
0
Fork 0
Code Issues 7 Pull Requests 2 Actions Packages Projects Releases Activity

content: Fix the typo

Browse Source
This commit is contained in:
Nikolai Rodionov 2023-03-29 17:29:47 +02:00
parent 5e19dbd9d8
commit 80cb94f767
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
content/posts/argocd-dynamic-environment-per-branch-part-1/index.md
View File

@ -217,7 +217,7 @@ spec:
app: badhouseplants app: badhouseplants
branch: main branch: main
chart_version: 0.3.6 chart_version: 0.3.6
# Image that is lates now, we'll get there later # Image that is latest now, we'll get there later
value: | value: |
hugo: hugo:
image: image:
@ -376,7 +376,7 @@ And now let's create a job like that:
- argocd app wait -l app=badhouseplants -l branch=$DRONE_BRANCH - argocd app wait -l app=badhouseplants -l branch=$DRONE_BRANCH
``` ```
And the last step would be to remove an application when branch is removed. It could be easy with `Gitlab` because there you can use `environments` and `triggers` for removing branch *(as I remember)* But with `drone` it seems to be harder. Because `drone` won't be triggered by a removed branch. And the last step would be to remove an application when branch is merged. It could be easy with `Gitlab` because there you can use `environments` and `triggers` for removing branch *(as I remember)* But with `drone` it seems to be harder. Because `drone` won't be triggered by a removed branch.
Maybe a pull request trigger could be used for that, but I've found another way, which may not be the best, obviously. Maybe a pull request trigger could be used for that, but I've found another way, which may not be the best, obviously.
I've enabled only `fast-forward` merge to the `main` that that means that after merging a Pull Request the commit will have the same `SHA`. So when merging to the main branch, I can use the commit hash to remove a generator. It also means that if I have one commit deployed to several environments, I will remove more that I want. But I don't think that it will be a problem in my case. If you're not a lonely developer, but a team, you may need to choose something else. I've enabled only `fast-forward` merge to the `main` that that means that after merging a Pull Request the commit will have the same `SHA`. So when merging to the main branch, I can use the commit hash to remove a generator. It also means that if I have one commit deployed to several environments, I will remove more that I want. But I don't think that it will be a problem in my case. If you're not a lonely developer, but a team, you may need to choose something else.