Replying to @codefloe@social.tchncs.de
@codefloe I think I might do that.
But honestly that's not cool that We cannot use other git forge than GitHub to publish in OpenTofu/Terraform Registry.
cichy1173
- My website
- https://cichy1173.eu
- GitHub
- https://github.com/cichy1173 verified
- Polski blog
- https://blog.cichy1173.eu verified
- Codeberg
- https://codeberg.org/cichy1173
RE: https://mastodon.social/@cichy1173/117022079171619512
For now we host provider code and packages on @codefloe and we test it internally using network mirror #terraform feature.
I want to publish the provider in official Registry in the future - but this requires pushing the code to #GitHub :(
cichy1173@cichy1173@mastodon.socialLooks like it works! Finally Terraform Provider that works with Zabbix 7.0. I wished for this for more than a year.
RE: https://mastodon.social/@cichy1173/116994074000409902
Ok, looks like everything moved to @codefloe .
I also redeployed my runners to connect them with CodeFloe, but theirs runners are so frickin' fast so I use them sometimes, to less intensive tasks, that are cool when are finished quickly while Docker images are built on my runners.
I also subscribed @codefloe on Librepay because I really like what they are doing.
cichy1173@cichy1173@mastodon.socialI moved cichyform repository with my custom Terraform modules to @codefloe . Original repository on codeberg has not been deleted but archived so your stacks should be usable without any migrations. But all tags and commits are migrated to CodeFloe, so just simple edit in source="" should be enough to migrate :-)
https://codefloe.com/cichy1173/cichyform
#terraform #forgejo #codefloe #opentofu
codefloe.com/cichy1173/cichyformLooks like it works! Finally Terraform Provider that works with Zabbix 7.0. I wished for this for more than a year.
ALT
I moved cichyform repository with my custom Terraform modules to @codefloe . Original repository on codeberg has not been deleted but archived so your stacks should be usable without any migrations. But all tags and commits are migrated to CodeFloe, so just simple edit in source="" should be enough to migrate :-)
https://codefloe.com/cichy1173/cichyform
#terraform #forgejo #codefloe #opentofu
codefloe.com/cichy1173/cichyform
CodeFloe - the Forgejo developer platformcichyformThis repository contains Terraform modules that I personally use in various infrastructure projects. Each module is versioned using Git tags for consistent and reproducible deployments. #terraform #opentofu #iacReplying to @codefloe@social.tchncs.de
@codefloe Will check this out. Thanks!
Replying to @codefloe@social.tchncs.de
@codefloe Yeah, no problem. The issue that i described is in the Forgejo web ui, not in your migration tool :-)
Replying to @cichy1173@mastodon.social
New Migration has some troubles, ie if you will check the Releases migration but the ori repository has this disabled, you will get an error🤐
I want to migrate repos and mirror them while still using old #Forgejo. When everything will be migrated I will just change origin URI in terminal and that's all!
(some ci/cd will need some changes though...)
Replying to @codefloe@social.tchncs.de
@codefloe Thanks! That's the level of support that I could even imagine 
This is what I did for two repositories already:
1. New Migration with API key to old Forgejo and linked repo
2. Adding auto mirroring in old forgejo using ssh link and ssh keys.
3. adding the ssh key to the CodeFloe
This is not great bc #forgejo generates new ED key for every repo that is being mirrored. And of course it is a lot of clicking.
Migrated two repos using New Migration feature from Forgejo to Forgejo ( @codefloe ) and i set mirroring to CodeFloe, but doing this manually in web browser is a pain in the a**. Is there an already existing tool that will help me automate this?