fix(Atracker): re-gen service after es s2s API changes and hand edits… #352
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
|
|
… for examples and IT Signed-off-by: Helen Xu <[email protected]>
helenxu1221
force-pushed
the
atracker-es-s2s
branch
from
c4078c7 to
933b198
Compare
ibm-devx-sdk
pushed a commit
that referenced
this pull request
Aug 30, 2024
## [0.68.1](v0.68.0...v0.68.1) (2024-08-30) ### Bug Fixes * **ATracker:** re-gen service after es s2s API changes and hand edits for examples and IT ([#352](#352)) ([f7efa3d](f7efa3d))
|
🎉 This PR is included in version 0.68.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
… for examples and IT
PR summary
add ServiceToServiceEnabled field to EventstreamsEndpointPrototype
PR Checklist
Please make sure that your PR fulfills the following requirements:
Current vs new behavior
current behavior: only plain text password is supported for event streams topic access.
new behavior: service to service authorization will be supported in addition to plain text password.
Does this PR introduce a breaking change?
Other information