-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
replacement transformer that uses the new replacement filter #3737
replacement transformer that uses the new replacement filter #3737
Conversation
plugin/someteam.example.com/v1/replacementtransformer/ReplacementTransformer.go
Outdated
Show resolved
Hide resolved
92096cc
to
b239e3a
Compare
b239e3a
to
eddb9fd
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A general question about release logistics: Unless there's an additional step I'm not aware of, it seems like this will expose the new field in the first release we make after merging. Given that, should this PR include docs changes (e.g. in examples/
)? Were we deferring the additional testing, and the rejection and field options implementations to a follow-up PR or potentially until a follow-up release?
plugin/builtin/replacementtransformer/ReplacementTransformer.go
Outdated
Show resolved
Hide resolved
@KnVerey Regarding your general questions I gave it some thought and I think you're right. I'll comment out exposing a replacements field in the kustomization file. It'll be better to add that with documentation in a later PR after everything else is in place. With this PR we can focus on the plugin itself and the other concerns you've brought up. |
eddb9fd
to
68d3f36
Compare
68d3f36
to
3f3db4f
Compare
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: natasha41575 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 |
db9bb26
to
9c06987
Compare
9c06987
to
038bc77
Compare
/lgtm We can tweak the ResMap api a bit to eliminate all those duplicated loops over resources that appear in plugins. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
@monopole thanks! I'll make documentation PRs when this is released |
Part of #3492.
This PR implements a basic builtin replacement transformer that is connected to a
replacements
field in the kustomization file.ALLOW_MODULE_SPAN