Skip to content

Conversation

mburke5678
Copy link
Contributor

@mburke5678 mburke5678 commented Sep 22, 2025

Updated example bearer token in response to InfoSec concern emailed to @dfitzmau

Cherrypick after #99294 is fully cherrypicked. This PR depends on a change in that PR.

namespace: my-namespace
data:
bearerToken: "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXV" <1>
bearerToken: "dG9rZW4=..." <1>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for raising this PR, @mburke5678 . I'm unsure if this example will still generate the security alert message. How about the following value?

<bearer_token>

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dfitzmau A boring, but safe option (dG9rZW4= is token in base64, tee-hee). Done.

@mburke5678 mburke5678 force-pushed the cma-change-token-example branch from a3d419d to f3d0b0e Compare September 22, 2025 15:49
Copy link

openshift-ci bot commented Sep 22, 2025

@mburke5678: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@dfitzmau
Copy link
Contributor

Thanks, @mburke5678 . LGTM. Please merge the PR to the appropriate branches.

@mburke5678 mburke5678 merged commit 18353b5 into openshift:main Sep 22, 2025
2 checks passed
@mburke5678 mburke5678 deleted the cma-change-token-example branch September 22, 2025 19:52
@mburke5678
Copy link
Contributor Author

/cherrypick enterprise-4.12

@openshift-cherrypick-robot

@mburke5678: new pull request created: #99731

In response to this:

/cherrypick enterprise-4.12

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@mburke5678
Copy link
Contributor Author

/cherrypick enterprise-4.13

@mburke5678
Copy link
Contributor Author

/cherrypick enterprise-4.14

@mburke5678
Copy link
Contributor Author

/cherrypick enterprise-4.15

@mburke5678
Copy link
Contributor Author

/cherrypick enterprise-4.16

@mburke5678
Copy link
Contributor Author

/cherrypick enterprise-4.17

@mburke5678
Copy link
Contributor Author

/cherrypick enterprise-4.18

@mburke5678
Copy link
Contributor Author

/cherrypick enterprise-4.19

@mburke5678
Copy link
Contributor Author

/cherrypick enterprise-4.20

@openshift-cherrypick-robot

@mburke5678: new pull request created: #99732

In response to this:

/cherrypick enterprise-4.13

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-cherrypick-robot

@mburke5678: new pull request created: #99733

In response to this:

/cherrypick enterprise-4.14

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-cherrypick-robot

@mburke5678: new pull request created: #99734

In response to this:

/cherrypick enterprise-4.15

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-cherrypick-robot

@mburke5678: new pull request created: #99735

In response to this:

/cherrypick enterprise-4.16

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-cherrypick-robot

@mburke5678: #99478 failed to apply on top of branch "enterprise-4.17":

Applying: CMA Update token example
Using index info to reconstruct a base tree...
M	nodes/cma/nodes-cma-autoscaling-custom-trigger-auth.adoc
Falling back to patching base and 3-way merge...
Auto-merging nodes/cma/nodes-cma-autoscaling-custom-trigger-auth.adoc
CONFLICT (content): Merge conflict in nodes/cma/nodes-cma-autoscaling-custom-trigger-auth.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 CMA Update token example

In response to this:

/cherrypick enterprise-4.17

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-cherrypick-robot

@mburke5678: new pull request created: #99736

In response to this:

/cherrypick enterprise-4.18

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-cherrypick-robot

@mburke5678: new pull request created: #99737

In response to this:

/cherrypick enterprise-4.19

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-cherrypick-robot

@mburke5678: #99478 failed to apply on top of branch "enterprise-4.20":

Applying: CMA Update token example
Using index info to reconstruct a base tree...
M	nodes/cma/nodes-cma-autoscaling-custom-trigger-auth.adoc
Falling back to patching base and 3-way merge...
Auto-merging nodes/cma/nodes-cma-autoscaling-custom-trigger-auth.adoc
CONFLICT (content): Merge conflict in nodes/cma/nodes-cma-autoscaling-custom-trigger-auth.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 CMA Update token example

In response to this:

/cherrypick enterprise-4.20

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants