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

Enhance APIApplicator with applying ApplyOption before creating #234

Closed
captainroy-hy opened this issue Dec 24, 2020 · 3 comments
Closed
Labels
enhancement New feature or request stale wontfix This will not be worked on

Comments

@captainroy-hy
Copy link

captainroy-hy commented Dec 24, 2020

What problem are you facing?

It's expected to allow ApplyOption works before creating as already mentioned in this comment,
That would make the Applicator operation more flexible.

How could Crossplane help solve your problem?

Is there any plan to make it work? Or any other concerns?

@captainroy-hy captainroy-hy added the enhancement New feature or request label Dec 24, 2020
@negz
Copy link
Member

negz commented Mar 14, 2021

@captainroy-hy Thanks for opening this! I'm not aware of anyone planning to work on this, but the functionality is still desirable. Contributions are definitely welcome. I will warn though that these Apply functions are very widely used across the Crossplane codebase and have historically proven tricky to change without subtly breaking things so whoever takes this on will need to be extra careful.

@stale
Copy link

stale bot commented Aug 13, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix This will not be worked on label Aug 13, 2022
Copy link

github-actions bot commented Sep 4, 2024

Crossplane does not currently have enough maintainers to address every issue and pull request. This issue has been automatically marked as stale because it has had no activity in the last 90 days. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh will mark this issue as not stale.

@github-actions github-actions bot added the stale label Sep 4, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request stale wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants