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

Ignore tags managed by external party #1177

Closed
kirek007 opened this issue Feb 28, 2024 · 5 comments
Closed

Ignore tags managed by external party #1177

kirek007 opened this issue Feb 28, 2024 · 5 comments
Labels
enhancement New feature or request is:triaged Indicates that an issue has been reviewed. stale

Comments

@kirek007
Copy link

What problem are you facing?

My AWS account are managed by organization that have automation in place that adds tags with known prefix to all resources create by me. These tags can not be created or changed by me.

How could Official AWS Provider help solve your problem?

Terraform-aws-provider provides an option to ignore tags by prefix, provider-wide. (Documentation)

My propose is to extend ProviderConfig with field that allows defining prefixes to ignore. This is later used in provided configuration here

apiVersion: aws.upbound.io/v1beta1
kind: ProviderConfig
metadata:
  name: default
spec:
  ignoreTags
    prefixes:
      - "platform_"
      - "managed_

What I've tried to mitigate issue:

  1. Simply add tags and
  2. Disable lateInit - Result:
    Message:               async update failed: failed to update the resource: [...] UnauthorizedOperation: You are not authorized to perform this operation.
    Reason:                AsyncUpdateFailure
    Status:                False
    Type:                  LastAsyncOperation
  1. Use InitProvider to create tags in advance - Not possible to update tags later

Solution:

I'm happy to contribute code, I've working PoC, PR will be provided shortly

@kirek007 kirek007 added enhancement New feature or request needs:triage labels Feb 28, 2024
@haarchri
Copy link
Member

xref: #1173

Copy link

github-actions bot commented Aug 8, 2024

This provider repo does not have enough maintainers to address every issue. Since there has been no activity in the last 90 days it is now marked as stale. 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 Aug 8, 2024
@haarchri
Copy link
Member

haarchri commented Aug 8, 2024

/fresh

@github-actions github-actions bot removed the stale label Aug 9, 2024
Copy link

github-actions bot commented Nov 7, 2024

This provider repo does not have enough maintainers to address every issue. Since there has been no activity in the last 90 days it is now marked as stale. 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 Nov 7, 2024
Copy link

This issue is being closed since there has been no activity for 14 days since marking it as stale. If you still need help, feel free to comment or reopen the issue!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request is:triaged Indicates that an issue has been reviewed. stale
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants