-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
config yaml guide updates #32869
config yaml guide updates #32869
Conversation
Thanks for your pull request! The title of your pull request does not follow our editorial rules. Could you have a look?
|
🙈 The PR is closed and the preview is expired. |
08aabf2
to
d5a8dca
Compare
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, I added a couple of comments but I'd like @radcortez to have a look too.
docs/src/main/asciidoc/config-your-quarkus-applications-using-a-yaml-file_howto.adoc
Outdated
Show resolved
Hide resolved
docs/src/main/asciidoc/config-your-quarkus-applications-using-a-yaml-file_howto.adoc
Outdated
Show resolved
Hide resolved
docs/src/main/asciidoc/config-your-quarkus-applications-using-a-yaml-file_howto.adoc
Outdated
Show resolved
Hide resolved
docs/src/main/asciidoc/config-your-quarkus-applications-using-a-yaml-file_howto.adoc
Outdated
Show resolved
Hide resolved
docs/src/main/asciidoc/config-your-quarkus-applications-using-a-yaml-file_howto.adoc
Outdated
Show resolved
Hide resolved
docs/src/main/asciidoc/config-your-quarkus-applications-using-a-yaml-file_howto.adoc
Outdated
Show resolved
Hide resolved
docs/src/main/asciidoc/config-your-quarkus-applications-using-a-yaml-file_howto.adoc
Outdated
Show resolved
Hide resolved
docs/src/main/asciidoc/config-your-quarkus-applications-using-a-yaml-file_howto.adoc
Outdated
Show resolved
Hide resolved
docs/src/main/asciidoc/config-your-quarkus-applications-using-a-yaml-file_howto.adoc
Outdated
Show resolved
Hide resolved
docs/src/main/asciidoc/config-your-quarkus-applications-using-a-yaml-file_howto.adoc
Outdated
Show resolved
Hide resolved
docs/src/main/asciidoc/config-your-quarkus-applications-using-a-yaml-file_howto.adoc
Outdated
Show resolved
Hide resolved
docs/src/main/asciidoc/config-your-quarkus-applications-using-a-yaml-file_howto.adoc
Outdated
Show resolved
Hide resolved
docs/src/main/asciidoc/config-your-quarkus-applications-using-a-yaml-file_howto.adoc
Outdated
Show resolved
Hide resolved
docs/src/main/asciidoc/config-your-quarkus-applications-using-a-yaml-file_howto.adoc
Outdated
Show resolved
Hide resolved
docs/src/main/asciidoc/config-your-quarkus-applications-using-a-yaml-file_howto.adoc
Outdated
Show resolved
Hide resolved
df3ce41
to
fcf093c
Compare
Thanks for your review and comments, @gsmet & @radcortez. I've made some updates based on your suggestions and left a few suggestions from @radcortez open so I can ask for clarification when we meet tomorrow. |
293e4e8
to
f97bb6c
Compare
f97bb6c
to
ba59762
Compare
769090e
to
283493e
Compare
634beb8
to
9c70135
Compare
626ac8d
to
8847b17
Compare
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 left a couple of additional comments. Once those are resolved, I think it should be good to go. Thanks!
8847b17
to
e47de51
Compare
I think @gsmet may still have some concerns. |
Hi @gsmet. I welcome your thoughts and comments. I'm getting ready to put it through our official QE process and want to make sure the content is settled before then. |
e47de51
to
994ff8c
Compare
994ff8c
to
4f8ad84
Compare
@gsmet I'm not sure whether to wait for your input. I've gone ahead and requested QE review via https://issues.redhat.com/browse/QUARKUS-3243. Please let me know if you would like me postpone. |
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.
Review updated to clarify my thoughts: I'm unhappy with the current result.
It is less precise, sometimes incorrect, and far more verbose than it used to be.
Developers don't have a lot of time when they read documentation. If we are making every small detail extremely verbose, they won't read our documentation.
Also we really need to avoid adding very vague sentences that are not actually useful.
I tried to point out some of the issues but really it's a general impression about this update.
|
||
Remove the `src/main/resources/application.properties` and create a `src/main/resources/application.yaml` file. | ||
In the YAML configuration file, you can define a nested element inside an existing element to set configuration properties for your {project-name} application. |
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 don't understand this sentence and what it brings to the plate?
I mean, this is the basics of YAML so it's not an extra feature or something that should be in a separate paragraph?
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 removed the "nested" term. This section is very basic but might help non-experts by showing an example configuration file. WDYT?
== Expressions | ||
// meta:include::modules/proc_setting-custom-configuration-profiles-with-yaml.adoc[leveloffset=+2] | ||
[id="proc_setting-custom-configuration-profiles-with-yaml_{context}"] | ||
== Setting custom configuration profiles with YAML |
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 don't understand the value of this paragraph compared to the previous one.
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.
Good point. Removed this section.
// DELETE meta:include::modules/con_external-application-yaml-file-for-configuring-properties-at-runtime.adoc[leveloffset=+1] | ||
// CREATE meta:include::modules/proc_configure-properties-at-run-time-external-yaml.adoc[leveloffset=+1] | ||
[id="proc_configure-properties-at-run-time-external-yaml_{context}"] | ||
== Configure properties at run time |
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.
Don't we write it runtime
? At least that's how we used to write it everywhere? Did it change?
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.
IBM Style states:
run time, runtime noun
- Write as two words to refer to the time at which an application runs (for example, “At run time, you can…”).
- Write as one word to refer to the environment in which an application runs (for example, “The Java runtime is
controlled by…”).
However, if you feel strongly about it, we can use runtime
. Most users are probably fine with it as a single word. Just let me know.
+ | ||
. To compile your {project-name} application in development mode, enter the following command from the project directory: | ||
+ | ||
.Compile your {project-name} application | ||
[source,bash] | ||
---- | ||
./mvnw quarkus:dev | ||
---- | ||
+ |
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'm not sure of the value of this here?
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.
Generally, this type of information is useful for non-expert users such as students. Red Hat generally gets complaints from newer users that our documentation assumes too much expertise or prior knowledge.
|
||
== Configuration key conflicts | ||
Structured formats such as YAML only support a subset of the possible configuration namespace. | ||
The following procedure shows how to resolve a conflict between two configuration properties, `quarkus.http.cors` and `quarkus.http.cors.methods`, where one property is the prefix of another. |
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'm not sure about the rules and maybe this needs to be discussed at a higher level but we are adding a ton of procedures/prerequisites and this adds a lot of noise when you are trying to find some information.
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.
Please feel free to strike any information that doesn't add value for our customers.
In future projects, rather than trying to merge the community and product content, I'll adopt an "additive" process. That is, I'll ask the SME to identify which product content they want to migrate to the community docs first.
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.
Or, if you feel like that's too much trouble, I can toss out this PR and we start over with the proposed "additive" process instead.
Thanks again for these additional comments. I'm making further updates and replying to some of your questions. |
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 your feedback, @gsmet. I've made updates and am open to more. Please have a look at my replies in the open conversations.
// DELETE meta:include::modules/con_external-application-yaml-file-for-configuring-properties-at-runtime.adoc[leveloffset=+1] | ||
// CREATE meta:include::modules/proc_configure-properties-at-run-time-external-yaml.adoc[leveloffset=+1] | ||
[id="proc_configure-properties-at-run-time-external-yaml_{context}"] | ||
== Configure properties at run time |
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.
IBM Style states:
run time, runtime noun
- Write as two words to refer to the time at which an application runs (for example, “At run time, you can…”).
- Write as one word to refer to the environment in which an application runs (for example, “The Java runtime is
controlled by…”).
However, if you feel strongly about it, we can use runtime
. Most users are probably fine with it as a single word. Just let me know.
|
||
== Configuration key conflicts | ||
Structured formats such as YAML only support a subset of the possible configuration namespace. | ||
The following procedure shows how to resolve a conflict between two configuration properties, `quarkus.http.cors` and `quarkus.http.cors.methods`, where one property is the prefix of another. |
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.
Please feel free to strike any information that doesn't add value for our customers.
In future projects, rather than trying to merge the community and product content, I'll adopt an "additive" process. That is, I'll ask the SME to identify which product content they want to migrate to the community docs first.
+ | ||
. To compile your {project-name} application in development mode, enter the following command from the project directory: | ||
+ | ||
.Compile your {project-name} application | ||
[source,bash] | ||
---- | ||
./mvnw quarkus:dev | ||
---- | ||
+ |
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.
Generally, this type of information is useful for non-expert users such as students. Red Hat generally gets complaints from newer users that our documentation assumes too much expertise or prior knowledge.
== Expressions | ||
// meta:include::modules/proc_setting-custom-configuration-profiles-with-yaml.adoc[leveloffset=+2] | ||
[id="proc_setting-custom-configuration-profiles-with-yaml_{context}"] | ||
== Setting custom configuration profiles with YAML |
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.
Good point. Removed this section.
|
||
== Configuration key conflicts | ||
Structured formats such as YAML only support a subset of the possible configuration namespace. | ||
The following procedure shows how to resolve a conflict between two configuration properties, `quarkus.http.cors` and `quarkus.http.cors.methods`, where one property is the prefix of another. |
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.
Or, if you feel like that's too much trouble, I can toss out this PR and we start over with the proposed "additive" process instead.
Closing this PR to stop adding to sunken costs. Starting over with updated priorities and methods. |
Fixes #32890