Update #1
Open
Update #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fix gogs hookPullRequest actionSync typo
Within the PR go-gitea/gitea#2184 on Gitea the project dropped the standard behavior to use x-auth-basic personal access token. So we should use a proper username and the token from now on to support Gitea >= 1.2.0. Since this driver anyway only supports Gitea >= 1.2.0 this won't be a breaking change on Drone side, the only breaking change is on side of Gitea!
Urgent fix for changed auth behavior on Gitea
Signed-off-by: Bo-Yi Wu <[email protected]>
Signed-off-by: Bo-Yi Wu <[email protected]>
Signed-off-by: Bo-Yi Wu <[email protected]>
Signed-off-by: Bo-Yi Wu <[email protected]>
fix missing commit sha and wrong tag link for Gitea.
In our current drone setup, we are not using a proxy, thus letting drone handle SSL termination. In addition, we are not exposing port 80 (effectively disabling insecure drone access). When new engineers join and attempt to access drone, they are not sent a 301 and often complain that they either do not have access or that drone is broken (when in reality they are just accessing drone via the incorrect protocol/port). This commit changes the default behavior when running drone with a server-cert by only sending redirects on port 80 rather than allowing both secure and insecure access.
This commit sets the http handler to the redirect function for let's encrypt enabled drone instances. In addition, the `Strict-Transport-Security` header is added to the redirect given `header.Secure` will only be added for gin routes. This commit resolves harness#2261.
…https-when-ssl-is-enabled Redirect HTTP to HTTPS when SSL is enabled.
bump minor version [ci skip]
fix(drone-server): missing default branch name in metadata.
…t-include-scheme Validate DRONE_HOST to ensure it contains a scheme and not a trailing slash
…t-include-scheme Fix DRONE_HOST check
Log the exact error in case of 'error setting commit status'
Update router.go
Fix gitea `actionSync`
Add ability to restart build of any state
Remove labels deserialization for gogs and gitea PRs
Added a feature to obtain the initial Vault token from the Kubernetes auth method. This works by making a request to the Vault server at the specified auth method mount point's login path and presenting the JWT located in a file on a running pod, along with the Kubernetes role to authenticate as. Vault will then respond with a token and its TTL, if the request is valid.
- read access - write access - admin access
Enable Vault auth through kubernetes auth method
full_name -> fullName "%s" -> %q errors.New -> fmt.Errorf
Use proper Bitbucket API for permission detection
Vault server response for lease_duration is an integer, rather than a string
Fix vault-k8s expected response type
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.