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

Use environment to matchLabels: #5553

Open
diegoavitorino opened this issue Apr 5, 2024 · 2 comments
Open

Use environment to matchLabels: #5553

diegoavitorino opened this issue Apr 5, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@diegoavitorino
Copy link

diegoavitorino commented Apr 5, 2024

Hi, I'd like to know is is possible to inform a environment in matchlabels:

instead:

matchLabels:
app: etl-app-dev

use:

matchLabels:
{some env from EnvironmentConfig}

thanks

@diegoavitorino diegoavitorino added the enhancement New feature or request label Apr 5, 2024
@bobh66
Copy link
Contributor

bobh66 commented Apr 8, 2024

Hi @diegoavitorino - can you provide some more context? Where is the matchLabels located? Is this part of a Composition? Thanks

@diegoavitorino
Copy link
Author

diegoavitorino commented Apr 8, 2024

Hi, exatly, for example, I've created a core label witch match all my composition:

patchSets:

  • name: common
    patches:
    • type: FromEnvironmentFieldPath
      fromFieldPath: label
      toFieldPath: metadata.labels['app']

each resource:

  patches:
    - type: PatchSet
      patchSetName: common  

until here it is ok, but, I'd like each matchlabel use the same way, use an env, instead put name by name .

        securityGroupIdSelector:
          matchLabels:
            app: **rds-app-dev** , use some common env instead
            
        dbSubnetGroupNameSelector:
          matchLabels:
            app: **rds-app-dev**   use some common env instead     
            
        vpcSecurityGroupIdSelector:
          matchLabels:
            app: **rds-app-dev**    use some common env instead                                    

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants