Bug 1734615: resourceapply: don't log secret data

[sttts]

Backport of #472

[openshift-ci-robot]

@sttts: An error was encountered searching the Bugzilla server at https://bugzilla.redhat.com for bug 1734615:

could not unmarshal response body: json: cannot unmarshal string into Go struct field Bug.alias of type int
Please contact an administrator to resolve this issue, then request a bug refresh with /bugzilla refresh.

Details

In response to this:

Bug 1734615: resourceapply: don't log secret data

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/test-infra repository.

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sttts

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [sttts]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[sttts]

/assign @enj

[sttts]

/bugzilla refresh

[openshift-ci-robot]

@sttts: An error was encountered searching the Bugzilla server at https://bugzilla.redhat.com for bug 1734615:

could not unmarshal response body: json: cannot unmarshal string into Go struct field Bug.alias of type int
Please contact an administrator to resolve this issue, then request a bug refresh with /bugzilla refresh.

Details

In response to this:

/bugzilla refresh

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/test-infra repository.

[sttts]

/bugzilla refresh

[openshift-ci-robot]

@sttts: An error was encountered searching the Bugzilla server at https://bugzilla.redhat.com for bug 1734615:

could not unmarshal response body: json: cannot unmarshal string into Go struct field Bug.alias of type int
Please contact an administrator to resolve this issue, then request a bug refresh with /bugzilla refresh.

Details

In response to this:

/bugzilla refresh

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/test-infra repository.

[enj]

/close

In favor of #495

[openshift-ci-robot]

@enj: Closed this PR.

Details

In response to this:

/close

In favor of #495

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/test-infra repository.

[sttts]

/bugzilla refresh

[openshift-ci-robot]

@sttts: This pull request references an invalid Bugzilla bug:

• expected the bug to target the "4.1.z" release, but it targets "---" instead
• expected dependent Bugzilla bug to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is POST instead
• expected dependent Bugzilla bug to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is NEW instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

Bug 1734615: resourceapply: don't log secret data

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/test-infra repository.

[sttts]

/bugzilla refresh

[openshift-ci-robot]

@sttts: This pull request references an invalid Bugzilla bug:

• expected the bug to target the "4.1.z" release, but it targets "---" instead
• expected dependent Bugzilla bug to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is POST instead
• expected dependent Bugzilla bug to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is NEW instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/bugzilla refresh

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/test-infra repository.