-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Updating the Service binding content #23726
Updating the Service binding content #23726
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.
Overall looks, good.
There are two chunks where I prefer the original text over the modified one.
<artifactId>quarkus-hibernate-orm</artifactId> | ||
</dependency> | ||
---- | ||
Users often use this concept of workload projection during the development time to connect their application to a dev-database, or other locally runned services, without changing the actual application code or configuration. |
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.
Where does this come from? I personally don't know anyone that does this...
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.
I have got this from my latest meeting with Ioannis. @iocanel
Maybe I just misunderstood something but thats what we got in the google doc
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.
Also, I have an upgrade for this:
During application development, users can use workload projection to connect their application to a dev-database, or other locally-run services, without changing the actual application code or configuration.
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.
This comes from me. I am not sure how extensively this pattern is used, but my understanding is that one of the benefits of workload projection compared to the traditional evn variable style of binding is the fact that it can be simpler to use in development, testing etc.
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.
.. and the other being security
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.
Yes, I added it since I find it valuable for the section.
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.
Looks better!
@iocanel has the final say on this
<artifactId>quarkus-hibernate-orm</artifactId> | ||
</dependency> | ||
---- | ||
Users often use this concept of workload projection during the development time to connect their application to a dev-database, or other locally runned services, without changing the actual application code or configuration. |
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.
This comes from me. I am not sure how extensively this pattern is used, but my understanding is that one of the benefits of workload projection compared to the traditional evn variable style of binding is the fact that it can be simpler to use in development, testing etc.
I have one last suggestion regarding of our headings in here: Just because action oriented headings should be only used for Procedures. |
I applied some minor language changes. My part is done for now. @geoand @iocanel What we can decide further on this subject is:
Thank you so much for great cooperation and kind feedback provided by @iocanel |
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 for this.
We will need the commits to be squashed
Sure, no problem. Will do when we will get the green light from @iocanel so that no more commits will be needed. |
Makes sense! |
Added some minor changes to the doc:
|
@geoand: It looks good to me. Can you please review my 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.
LGTM
@MichalMaler can you please squash all changes including mine, so that we can merge? |
Will do! With a pleasure :) But sirs, I need to say that this chapter will be so good now, that it wont be fair in comparison with the rest of the document :D Great work all of you. |
40ea137
to
5e6a891
Compare
5e6a891
to
2b1c18f
Compare
2b1c18f
to
db1ad62
Compare
Reviewed, squashed, rebased. |
db1ad62
to
5f374b6
Compare
Signed-off-by: Michal Maléř <[email protected]> Applying suggestions from the SME review Signed-off-by: Michal Maléř <[email protected]> Vale fixes Signed-off-by: Michal Maléř <[email protected]> Style tuning Signed-off-by: Michal Maléř <[email protected]> Applying suggestions from the SME review Signed-off-by: Michal Maléř <[email protected]> Language fixes Signed-off-by: Michal Maléř <[email protected]> Language fixes Signed-off-by: Michal Maléř <[email protected]> doc: minor changes in service binding doc
5f374b6
to
33c74b9
Compare
A draft for a possible update of this chapter has been created under cooperation with Ioannis Kanellos.
Signed-off-by: Michal Maléř [email protected]