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

Documentation and project description #6

Merged
merged 3 commits into from
Jan 15, 2025
Merged

Documentation and project description #6

merged 3 commits into from
Jan 15, 2025

Conversation

CDimonaco
Copy link
Member

Description

This PR aims to provide a basic documentation on how the operator works and the documentation for saptuneapplysolution operator.

@CDimonaco CDimonaco added the documentation Improvements or additions to documentation label Jan 14, 2025
@CDimonaco CDimonaco requested a review from arbulu89 January 14, 2025 12:56
@CDimonaco CDimonaco self-assigned this Jan 14, 2025
@CDimonaco CDimonaco requested review from balanza and arbulu89 and removed request for arbulu89 and balanza January 14, 2025 12:56
Copy link
Member

@nelsonkopliku nelsonkopliku left a comment

Choose a reason for hiding this comment

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

Thanks for this.

I could not but notice a parallelism between this

The minimum required version is 3.1.0. If saptune is not installed or the version does not meet the minimum requirement

and what we might already be happening in checks.

Is it correct to assume that very likely every operator would check something like that in the plan phase?

@CDimonaco
Copy link
Member Author

CDimonaco commented Jan 14, 2025 via email

Copy link

@arbulu89 arbulu89 left a comment

Choose a reason for hiding this comment

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

Really good!
Thank you

README.md Outdated
![flowchart](./flow_chart.png)

An operator is a unit of code that can perform write operations on target machines.
A write operation can either fail or succeed. If it succeeds, the operation will display a diff highlighting the changes before and after the commit phase.

Choose a reason for hiding this comment

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

I'm always in favor of using present term:
the operation displays a diff..

Copy link
Member Author

Choose a reason for hiding this comment

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

done

README.md Outdated
#### COMMIT

The COMMIT phase executes the actual write operations on the system, utilizing the information collected during the PLAN phase.
If an error occurs during this phase, a rollback will be triggered.

Choose a reason for hiding this comment

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

a rollback is triggered

Copy link
Member Author

Choose a reason for hiding this comment

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

done

README.md Outdated
If an error occurs during this phase, a rollback will be triggered.

The COMMIT phase should be idempotent. If a requested change has already been applied, the commit operation is simply skipped without returning an error.
Maintaining idempotency should be implemented appropriately based on the type of operations to be performed.

Choose a reason for hiding this comment

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

I think the Maintaining word is not needed here. Simply Idempotency should be...

Copy link
Member Author

Choose a reason for hiding this comment

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

done

@CDimonaco CDimonaco merged commit e2b8477 into main Jan 15, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Development

Successfully merging this pull request may close these issues.

3 participants