Skip to content

Commit 115b73f

Browse files
authored
fixed bad link url
1 parent cfdc040 commit 115b73f

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

docs/_posts/2025-07-07-gitops-in-backstage-templates.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -119,7 +119,7 @@ Again, the point here is that the backstage template will create a new file with
119119

120120
One could conceivably construct a helm chart but at that point you are making things complicated without the fun part which is what this post is all about!
121121

122-
It then dawned on me that I already have the ~~perfect~~ solution from [my post about cdk8s in argocd](./cdks8s-through-argocd).
122+
It then dawned on me that I already have the ~~perfect~~ solution from [my post about cdk8s in argocd](./cdk8s-through-argocd).
123123

124124
### cdk8s
125125

@@ -238,4 +238,4 @@ And once that information makes its way into kubernetes, crossplane will sync it
238238
239239
## Wrap up
240240
241-
Great, so now I can have my backstage template clone the gitops repo, add the file with the hostname that my application should have, once synched we can surf to that address and be served a working application. Once I grow tired of this app we just remove the file together with the rest of the application configuration and the valid callback urls for the client in keycloak get fewer.
241+
Great, so now I can have my backstage template clone the gitops repo, add the file with the hostname that my application should have, once synched we can surf to that address and be served a working application. Once I grow tired of this app we just remove the file together with the rest of the application configuration and the valid callback urls for the client in keycloak get fewer.

0 commit comments

Comments
 (0)