William Parr

feat: automatic branch creation for resource 'github_repository_file'

2

Resolves #2101 ---- ### Before the change? * Currently [repository_file](https://registry.terraform.io/providers/integrations/github/latest/docs/resources/repository_file) does not support automatic creation of branches. This means in order manage files via pull requests (rather than directly pushing...

feat: support signed commits for resource 'github_repository_file'

10

Resolves #879 ---- ### Before the change? * Currently github_repository_file modifies files via the github content API. Which means there is limited support for signed commits (ie. anything which supports...

[FEAT]: github_repository_file should support automatic branch creation if the ref does not exist

1

### Describe the need The resource github_repository_file does not currently support automatic branch creation. For example, a potential use case is rather than directly writing changes to a long lived...

fix(applicationset): prevent applicationset progressive sync from stalling in pending

19

Fixes https://github.com/argoproj/argo-cd/issues/12459 ApplicationSet Controller Progressive Sync sometimes looks to get into a state where the Applications are never synced and a rollout never concludes, based on the timestamps where an...

**Describe the bug** Currently only the manifest list appears to be signed, and has sigstore attachments pushed to ghcr. ```sh $ cosign triangulate ghcr.io/external-secrets/external-secrets@`crane digest ghcr.io/external-secrets/external-secrets:v0.9.13` ghcr.io/external-secrets/external-secrets:sha256-bc0348aa984c606de7c92f3313952ff4f8daf88f4913956e1ef18f9f2d4bf33d.sig $ crane manifest...

Misleading logs from monitorCatchpointCatchup

1

### Subject of the issue having deployed a new instance of Conduit, and an associated follower algod node. Seeing logs from https://github.com/algorand/conduit/blob/83dec6a37e0bac87209575e3a23597326547fb7f/conduit/plugins/importers/algod/algod_importer.go#L127C7-L127C7 Which misleadingly seems like it's stuck in processing...

feat: support securityContext and podSecurityContext configuration

1

Fixes https://github.com/topolvm/pvc-autoresizer/issues/264 Adds two new helm values controller.securityContext, and controller.podSecurityContext - these correspond to Container level Security Context and Pod level Security Context respectively. This may be leveraged to setup...

**What should the feature do:** Allow the configuration of [SecurityContext](https://kubernetes.io/docs/tasks/configure-pod-container/security-context/) at the level of the entire Pod, or from just the Container. **What is use case behind this feature:** The...

Support Witnessing Sigstore Signing with a Timestamp Authority Server

1

Github Artifact Attestation https://github.blog/changelog/2024-06-25-artifact-attestations-is-generally-available/ only uses public good rekor and fulcio for public repositories. For private repositories it supports usage of the following github hosted instances (note it does not...

Support github artifact attestation

3

Github recently launched https://github.blog/changelog/2024-06-25-artifact-attestations-is-generally-available/, which builds on sigstores https://github.com/sigstore/fulcio, https://github.com/sigstore/rekor and https://github.com/sigstore/timestamp-authority For public repos - there isn't really any concern here, as artifact attestations wraps the public good sigstore...