-
Notifications
You must be signed in to change notification settings - Fork 593
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
integrationArtifactTransport Command #4131
integrationArtifactTransport Command #4131
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Few typos
|
||
With this step, you can transport SAP Cloud Integration content across various landscapes using SAP Content Agent Service. | ||
|
||
SAP Cloud Integration provides content transport mechanism. SAP Content Agent service enables you to assemble the content from these content providers in MTAR format. Later, this content is either available for download or exported to the configured transport queue, such as SAP Cloud Transport Management. For more information on |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you explain just a bit more what you mean by "SAP Cloud Integration provides content transport mechanism."? Do you mean that SAP Cloud Integration is a content provider? (You mention content providers in the next sentence, but which content providers do you mean?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
reverted
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there is a separate review happen for documentation part by the Documentation experts, i would suggest not review the .md. .yaml content in detail
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since the documentation is my main way (and probably the main way for other people) to understand what this step is supposed to do, I would like a bit more explanation there if you could add that. When will the documentation experts review this? I can wait to add my review until they've made changes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After the documentation review, I'm still left with some questions about what exactly this step does and what the documentation is saying. Could you please elaborate on "SAP Cloud Integration provides content transport mechanism." Is there any other documentation you could link here? Also you mention content providers in the next sentence, but which content providers do you mean?
Since I'm not a Integration Suite expert, my suggestions won't be completely accurate. @AnnikaGonnermann and @axelalbrechtsap maybe you could support here with adding more detail to the documentation from the point of view of Integration Suite? I think it should be written for someone that has no idea what this step should do.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2 points:
- "SAP Cloud Integration provides content transport mechanism" used in the already referred public documentation which we also used as is (https://help.sap.com/docs/CONTENT_AGENT_SERVICE/ae1a4f2d150d468d9ff56e13f9898e07/8e274fdd41da45a69ff919c0af8c6127.html)
- there is blog linked in the last step which provide step by step instruction how to do integration package transport with CAS, TMS (https://blogs.sap.com/2022/03/25/transport-sap-cloud-integration-ci-cpi-content-with-transport-management-service-tms-and-content-agent-service-cas/)
i feel this is good enough from documentation standpoint.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since I'm not sure how to test this, could you please upload some sort of evidence that it worked properly? A screenshot of logs maybe? (of course without any sensitive information)
TMSQueue : Logs: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Documentation suggestions. Please let me know if I've misunderstood the step 🙂
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @mayurmohan! 🙂
/it |
1 similar comment
/it |
@I050368 and @srinikitha09 could you sign the license agreement? |
@mayurmohan are you I050368? It looks like some tests are failing because "I050368" hasn't signed the license agreement |
"I050368 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account." |
/it |
860f804
to
e6803cb
Compare
Co-authored-by: Srinikitha Kondreddy <[email protected]>
Co-authored-by: Srinikitha Kondreddy <[email protected]>
Co-authored-by: Linda Siebert <[email protected]>
e6803cb
to
c547de5
Compare
/it |
* integrationArtifactTransport Command * CodeReview Fix * CodeReview Fix * codereview fix * Update documentation/docs/steps/integrationArtifactTransport.md Co-authored-by: Srinikitha Kondreddy <[email protected]> * Update documentation/docs/steps/integrationArtifactTransport.md Co-authored-by: Srinikitha Kondreddy <[email protected]> * CodeReview Fixes * CodeReview FIxes * CodeReview Fix * Doc Fixes * Update documentation/docs/steps/integrationArtifactTransport.md Co-authored-by: Linda Siebert <[email protected]> * Doc fixes * Doc Fixes * CodeReview Fixes * Doc Fixes Co-authored-by: Linda Siebert <[email protected]> Co-authored-by: Srinikitha Kondreddy <[email protected]> Co-authored-by: Linda Siebert <[email protected]>
Changes
integrationArtifactTransport Command :- Integration artifact content transport using SAP Content Agent service