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

docs: Document ApplyOutOfSyncOnly in application spec #16282

Conversation

matthewhughes-uw
Copy link
Contributor

I found this being used in an application I was working on but had a hard time discovering its meaning since it wasn't in the specification[1] though it was in the sync-options docs (see also baa0f2e)

[1] https://argo-cd.readthedocs.io/en/stable/user-guide/application-specification/
[2] https://argo-cd.readthedocs.io/en/stable/user-guide/sync-options/#selective-sync

Checklist:

  • Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
  • The title of the PR states what changed and the related issues number (used for the release note). No: no release notes needed
  • The title of the PR conforms to the Toolchain Guide
  • I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue. No: no issue
  • I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them. No: not a new feature
  • Does this PR require documentation updates?
  • I've updated documentation as required by this PR.
  • Optional. My organization is added to USERS.md.
  • I have signed off all my commits as required by DCO
  • I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged. No: just docs changed
  • My build is green (troubleshooting builds).
  • My new feature complies with the feature status guidelines. No: no new feature
  • I have added a brief description of why this PR is necessary and/or what this PR solves. See PR description/commit body

@matthewhughes-uw matthewhughes-uw force-pushed the document-applyoutofsync-in-application-specification branch from 1a9b2f4 to 85a57d1 Compare November 8, 2023 11:38
@matthewhughes-uw
Copy link
Contributor Author

matthewhughes-uw commented Nov 8, 2023

Failing lint job is unrelated, looks to be addressed in #16275

EDIT: rebasing to include those changes fixed the issues in the Go tests/linting but there remain failures in the UI integration tests. As far as I can tell these are unrelated to the doc changes (the same failures are present in the latest build on master)

EDIT EDIT: the UI tests should be fixed with #16287

@matthewhughes-uw matthewhughes-uw marked this pull request as ready for review November 8, 2023 12:46
@matthewhughes-uw matthewhughes-uw requested review from a team as code owners November 8, 2023 12:46
@matthewhughes-uw matthewhughes-uw force-pushed the document-applyoutofsync-in-application-specification branch from 85a57d1 to c304160 Compare November 8, 2023 12:47
Copy link
Member

@ishitasequeira ishitasequeira left a comment

Choose a reason for hiding this comment

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

Thanks @matthewhughes-uw, LGTM!

@ishitasequeira ishitasequeira enabled auto-merge (squash) November 9, 2023 04:48
I found this being used in an application I was working on but had a
hard time discovering its meaning since it wasn't in the
specification[1] though it was in the `sync-options` docs[2] (see also
baa0f2e)

[1] https://argo-cd.readthedocs.io/en/stable/user-guide/application-specification/
[2] https://argo-cd.readthedocs.io/en/stable/user-guide/sync-options/#selective-sync

Signed-off-by: Matt Hughes <mhughes@uw.co.uk>
auto-merge was automatically disabled November 9, 2023 15:10

Head branch was pushed to by a user without write access

@matthewhughes-uw matthewhughes-uw force-pushed the document-applyoutofsync-in-application-specification branch from c304160 to 93e9752 Compare November 9, 2023 15:10
Copy link

codecov bot commented Nov 9, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (b33b7fa) 49.52% compared to head (93e9752) 49.52%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master   #16282   +/-   ##
=======================================
  Coverage   49.52%   49.52%           
=======================================
  Files         269      269           
  Lines       46990    46990           
=======================================
  Hits        23272    23272           
  Misses      21435    21435           
  Partials     2283     2283           

see 1 file with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@matthewhughes-uw
Copy link
Contributor Author

Thanks @matthewhughes-uw, LGTM!

Thanks for the review @ishitasequeira. I've forced pushed the branch after rebasing to include the CI fix from #16287 which dismissed your auto merge

@ishitasequeira ishitasequeira merged commit 3d6568d into argoproj:master Nov 9, 2023
22 checks passed
jmilic1 pushed a commit to jmilic1/argo-cd that referenced this pull request Nov 13, 2023
I found this being used in an application I was working on but had a
hard time discovering its meaning since it wasn't in the
specification[1] though it was in the `sync-options` docs[2] (see also
baa0f2e)

[1] https://argo-cd.readthedocs.io/en/stable/user-guide/application-specification/
[2] https://argo-cd.readthedocs.io/en/stable/user-guide/sync-options/#selective-sync

Signed-off-by: Matt Hughes <mhughes@uw.co.uk>
Signed-off-by: jmilic1 <70441727+jmilic1@users.noreply.github.com>
vladfr pushed a commit to vladfr/argo-cd that referenced this pull request Dec 13, 2023
I found this being used in an application I was working on but had a
hard time discovering its meaning since it wasn't in the
specification[1] though it was in the `sync-options` docs[2] (see also
baa0f2e)

[1] https://argo-cd.readthedocs.io/en/stable/user-guide/application-specification/
[2] https://argo-cd.readthedocs.io/en/stable/user-guide/sync-options/#selective-sync

Signed-off-by: Matt Hughes <mhughes@uw.co.uk>
tesla59 pushed a commit to tesla59/argo-cd that referenced this pull request Dec 16, 2023
I found this being used in an application I was working on but had a
hard time discovering its meaning since it wasn't in the
specification[1] though it was in the `sync-options` docs[2] (see also
baa0f2e)

[1] https://argo-cd.readthedocs.io/en/stable/user-guide/application-specification/
[2] https://argo-cd.readthedocs.io/en/stable/user-guide/sync-options/#selective-sync

Signed-off-by: Matt Hughes <mhughes@uw.co.uk>
lyda pushed a commit to lyda/argo-cd that referenced this pull request Mar 28, 2024
I found this being used in an application I was working on but had a
hard time discovering its meaning since it wasn't in the
specification[1] though it was in the `sync-options` docs[2] (see also
baa0f2e)

[1] https://argo-cd.readthedocs.io/en/stable/user-guide/application-specification/
[2] https://argo-cd.readthedocs.io/en/stable/user-guide/sync-options/#selective-sync

Signed-off-by: Matt Hughes <mhughes@uw.co.uk>
Signed-off-by: Kevin Lyda <kevin@lyda.ie>
Hariharasuthan99 pushed a commit to AmadeusITGroup/argo-cd that referenced this pull request Jun 16, 2024
I found this being used in an application I was working on but had a
hard time discovering its meaning since it wasn't in the
specification[1] though it was in the `sync-options` docs[2] (see also
baa0f2e)

[1] https://argo-cd.readthedocs.io/en/stable/user-guide/application-specification/
[2] https://argo-cd.readthedocs.io/en/stable/user-guide/sync-options/#selective-sync

Signed-off-by: Matt Hughes <mhughes@uw.co.uk>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants