Skip to content
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

Update Readme with the optional retry CR parameters #121

Merged

Conversation

clobrano
Copy link
Contributor

@clobrano clobrano commented Jan 8, 2024

No description provided.

Copy link
Contributor

openshift-ci bot commented Jan 8, 2024

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci openshift-ci bot added the approved label Jan 8, 2024
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
@clobrano clobrano force-pushed the update-readme-fa-retry-options/0 branch from 20d985a to e6f60dd Compare January 15, 2024 09:11
Copy link
Member

@razo7 razo7 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
left a nit and a general question that came to me from your PR.
Please update PR description and link it to the old and relevant PR
/hold
Feel free to unhold if want to discard my NIT

README.md Outdated Show resolved Hide resolved
README.md Outdated
Comment on lines 104 to 105
* `sharedparameters` - common cluster nodes information for executing the fence agent
* `nodeparameters` - specific cluster nodes information for executing the fence agent
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mentioning the next three parameters as optional and not mentioning these two as optional means that they are not optional.
In practice they are optional, even though I don't see a case where a user won't use/set them, thus I am leaning towards setting them as non-optional parameters or simply remove the omitempty. WDYT?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess they are optional just because it's up to the user to decide which specific parameters they want, but you're right that this way is confusing. I might rephrase the last three as "If unset, the default value is..." ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's up to the user to decide which specific parameters they want

and IF they want it. I think it is ok to keep them optional

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"If unset, the default value is..." ?

Or just remove the optional words. Optional parameter, default is "5s". -> Default is "5s".
I don't have a strong preference here.

I think it is ok to keep them optional

Agreed. My question was more about the sharedparameters and nodeparameters which maybe should not be optional. Without them running the fence agent would fail as it misses some parameters.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was referring to sharedparameters and nodeparameters too :)

Without them running the fence agent would fail as it misses some parameters

but I didn't realized that. They're surely not optional then

Copy link
Member

@razo7 razo7 Jan 16, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They're surely not optional then

Yes, I was just looking for another point of view to assert my assumption before taking an action :)

@razo7 razo7 marked this pull request as ready for review January 16, 2024 06:49
Copy link
Contributor

openshift-ci bot commented Jan 16, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: clobrano, razo7

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

The pull request process is described here

Needs approval from an approver in each of these files:

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

README.md Outdated
The CR includes the following parameters:

* `agent` - fence-agent name
* `sharedparameters` - common cluster nodes information for executing the fence agent
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not 100% sure if I have the meaning of these CR fields right in my head... but from here I don't really get it 🤔

IIUC:

  • sharedparameters - cluster wide parameters for executing the fence agent
  • nodeparameters - node specific parameters for executing the fence agent

WDYT?
@clobrano @razo7

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is kind of similar.
I think common cluster nodes information is just saying in different words that it is cluster wide parameters without repeating the word parameters for explaining sharedparameters.
I don't have a strong preference, even though your suggestion might be just more accurate.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like @slintes version too, thanks!

@clobrano clobrano force-pushed the update-readme-fa-retry-options/0 branch from d331b5a to 6bc2d84 Compare January 17, 2024 13:25
@razo7
Copy link
Member

razo7 commented Jan 17, 2024

/lgtm

@openshift-ci openshift-ci bot added the lgtm label Jan 17, 2024
@clobrano
Copy link
Contributor Author

/unhold

@openshift-merge-bot openshift-merge-bot bot merged commit 94c8050 into medik8s:main Jan 17, 2024
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants