v0.2.0
End-users features ✨
RemoteSyncer
RBAC checker
When creating, updating or deleting a RemoteSyncer
, a webhook will take care of checking if the user who has made the operation has the permission to access the resources listed in scopedResources
(for create
, update
or delete
).
Add short names for CRDs
ru
&rus
forRemoteUser
rub
&rubs
forRemoteUserBinding
rsy
&rsys
forRemoteSyncer
Migrating from the syngit.syngit.io
apiVersion to syngit.io
If the operator is upgraded using helm
, then the process is fully automated.
"syngit.syngit.io/associated-remote-userbinding": "true"
annotation (used in RemoteUser
) must be changed to "syngit.io/associated-remote-userbinding": "true"
.
Internal features 🌱
Linter
Add a linter job to the github workflow
Implement more tests
- Multiple concurrent
RemoteSyncer
test (9.)
When exactly two same remotesyncers exist (same target repo/branch, same scoped resources), it check that the webhook failed because the commit hash are not the same. The validation webhooks run in parallel. This behavior is intended (locked mutex). In a future version, a retry behavior will be implemented (see 📜 Roadmap). RemoteUser
update does not automatically add a new entry in theremoteRefs
of the associatedRemoteUserBinding
Add test utilities make fast-e2e
& make cleanup-e2e
(see 🚀 Tests)
Bug fixes 🐛
- When an update was made on a
RemoteUser
, then a new entry was added to theremoteRefs
of the associatedRemoteUserBinding
. - There was an error in the conversion webhook of the
RemoteUser
which was spamming the log of the controller. Now a default value is set instead of returning an error.
Package release 📦
Docker image:
ghcr.io/syngit-org/syngit:v0.2.0
Helm chart:
https://syngit-org.github.io/syngit version 0.2.0
Helm install
helm repo add syngit https://syngit-org.github.io/syngit
helm repo update syngit
helm install syngit syngit/syngit --version 0.2.0 -n <SYNGIT_NAMESPACE>
Helm upgrade
helm repo update syngit
helm upgrade -n <SYNGIT_NAMESPACE> syngit syngit/syngit