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.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use replaceOnChanges instead of hardcoded provider logic for custom replace behavior #1775

Open
lblackstone opened this issue Oct 19, 2021 · 1 comment
Open

Use replaceOnChanges instead of hardcoded provider logic for custom replace behavior #1775

lblackstone opened this issue Oct 19, 2021 · 1 comment
Labels
area/resource-management Issues related to Kubernetes resource provisioning, management, await logic, and semantics generally customer/feedback Feedback from customers kind/enhancement Improvements or new features

Comments

@lblackstone
Copy link
Member

Hello!

  • Vote on this issue by adding a 馃憤 reaction
  • If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

We currently specify replace behavior for certain resource properties directly in the provider. Now that we have the replaceOnChanges option available in the schema, we should use that instead to make it easier for users to override this behavior.

Related to #1568

Affected area/feature
@lblackstone lblackstone added kind/enhancement Improvements or new features area/resource-management Issues related to Kubernetes resource provisioning, management, await logic, and semantics generally labels Oct 19, 2021
@lblackstone lblackstone mentioned this issue Oct 19, 2021
Open
@lblackstone lblackstone mentioned this issue Dec 14, 2021
Open
@lblackstone lblackstone mentioned this issue Jan 4, 2022
Closed
@SharpEdgeMarshall
Copy link
Contributor

This is a critical issue for people managing aws-auth of eks with Pulumi, there's an ETA?

@viveklak viveklak added the customer/feedback Feedback from customers label Feb 4, 2022
@viveklak viveklak self-assigned this Mar 4, 2022
This was referenced Mar 9, 2022
Open
Merged
@lblackstone lblackstone mentioned this issue Jan 18, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/resource-management Issues related to Kubernetes resource provisioning, management, await logic, and semantics generally customer/feedback Feedback from customers kind/enhancement Improvements or new features
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@viveklak @SharpEdgeMarshall @lblackstone