Dynamic evns #15

Closed
opened 2023-02-22 15:58:52 +00:00 by allanger · 2 comments
allanger commented 2023-02-22 15:58:52 +00:00 (Migrated from git.badhouseplants.net)

I want to have an env for each branch. So I can really see my changes every time I'm pushing. And I don't have to test on the real production blog

I want to have an env for each branch. So I can really see my changes every time I'm pushing. And I don't have to test on the real production blog
allanger commented 2023-02-22 16:00:58 +00:00 (Migrated from git.badhouseplants.net)

Since everything is now migrated to helmfile, and argocd is freed up. I think I can use argocd for creating dynamic environments.

Since everything is now migrated to helmfile, and argocd is freed up. I think I can use argocd for creating dynamic environments.
allanger commented 2023-02-25 11:29:10 +00:00 (Migrated from git.badhouseplants.net)

Logic should be like that:

  • When a new branch is created, a new application is deployed
  • On each commit, env should be updated
  • When branch is removed, env should be gone
Logic should be like that: - When a new branch is created, a new application is deployed - On each commit, env should be updated - When branch is removed, env should be gone
This repo is archived. You cannot comment on issues.
1 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: badhouseplants/badhouseplants-net-old#15
No description provided.