centraldogma icon indicating copy to clipboard operation
centraldogma copied to clipboard

Highly-available version-controlled service configuration repository based on Git, ZooKeeper and HTTP/2

Results 166 centraldogma issues
Sort by recently updated
recently updated
newest added

Motivation: It is undesirable for repositories to be created with a `.git` suffix due to potential conflicts or confusion with Git's repository structure and management. Modifications: - Disallow creating a...

defect

### motivation: * Resolve https://github.com/line/centraldogma/issues/906 * A lot of effort is used to change permissions. ### modification: * Change admin from true to false or vice versa. ### result:

new feature

To simplify the operation that uses the repository name such as the authorization system. GitHub also removes the suffix automatically when creating a repository.

defect

### Motivation When unspecified a branch name on mirroring setup, the message show with `#null`, we should omit #null when using the default branch to avoid confuse. Result Close: https://github.com/line/centraldogma/issues/933

Motivation: It isn't easy to check how many commits have been pushed to a specific repository without looking at log files. This PR is the orignal commit of #943 that...

new feature

Motivation: This PR tries to solve the flakiness of `ServerStatusManagerIntegrationTest` in a different way. See #948 This workaround minimizes port collisions by ensuring that all ports are available when a...

cleanup

Seem it is a random fail, can we fix it? ``` ReplicatedLoginAndLogoutTest > loginAndLogout() FAILED java.util.concurrent.CompletionException: io.netty.channel.unix.Errors$NativeIoException: bind(..) failed: Address already in use at java.util.concurrent.CompletableFuture.reportJoin(CompletableFuture.java:375) at java.util.concurrent.CompletableFuture.join(CompletableFuture.java:1947) at com.linecorp.armeria.common.util.EventLoopCheckingFuture.join(EventLoopCheckingFuture.java:87) at...

When unspecified a branch name, the message show `#null`. Should we improve it? ![image](https://github.com/line/centraldogma/assets/11583408/2f164675-d8fc-41a5-b696-3190a90c4b2c)

Currently, an access log entry doesn't contain the actual role (OWNER, MEMBER or GUEST) of the user/app for the request. If such information is logged, an administrator could easily figure...

new feature

I have struggled on my attempt to set a git-cd mirroring from GitHub with a fine-grained access token. So wanted to document some of the things, On, page for mirroring...

documentation