Bernd Farka

@lengrongfu : do you mean the secret produced by crossplane? ``` Name: harbor-poc-connection-secret Namespace: my-harbor-ns Type: connection.crossplane.io/v1alpha1 Data ==== port: 1 bytes username: 10 bytes endpoint: 77 bytes ```

@cyrille-leclerc: > The value of `ci.pipeline.id` being `path/to/Build/pr-{number}` rather than `path/to/Build/job/PR-123/1` looks definitively like a bug. THX, this fix would help a lot. About the cardinality on the root span...

@cyrille-leclerc : we are doing our own processing of spans so there the name PR-{number} simply was misleading, plus i had no other chance since, as mentioned above, `ci.pipeline.id` also...

@cyrille-leclerc : if you don't mind volunteer for creating this PR...

Just to sum it up what the pr should include: * changing the name of the span to the pipeline name. * shouldn't be this done for branches to? (cardinality...

I would be open to contributing something similar like that snipplet to https://github.com/actions/runner-container-hooks/blob/main/packages/k8s/src/k8s/index.ts#L98 ``` if (useKubeScheduler()) { const affinity = new k8s.V1Affinity() affinity.nodeAffinity = new k8s.V1NodeAffinity() const nodeSelector = new...

@mzagozen / @pje / @chrispat / @DanRigby / @joshmgross : may I kindly ask you for feedback on this Feature Request?

@hectorj2f THX for you response! I see various problems in defining it with `VAULT_KEY_PREFIX`: * me as the verifier of an signature i most probably do not know the version...

@hectorj2f: I would be open for helping implementing the fix, since i have a valid test-setup up and running. The question for me is: what should be the solution? would...

From the Vault Documentation (https://learn.hashicorp.com/tutorials/vault/eaas-transit#rotate-the-encryption-key) > > One of the benefits of using the Vault transit secrets engine is its ability to easily rotate encryption keys. Keys can be rotated...