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

The cloud.provider fact still calls EC2 despite EC2 being in the block list #2690

Open
tvpartytonight opened this issue Mar 19, 2024 · 0 comments
Labels
accepted Valid issue that we intend to work on when we have the bandwidth bug Something isn't working

Comments

@tvpartytonight
Copy link
Contributor

tvpartytonight commented Mar 19, 2024

Describe the Bug

Even if EC2 is in the blocklist for facter, the cloud.provider fact will still make a call to EC2. The spot where it calls EC2 is here.

Expected Behavior

When EC2 is in the blocklist for facts, no calls should be made to EC2.

Workaround

Add the cloud.provider fact in the blocklist as well as EC2 to prevent the call.

Additional Context

Is related to #2672

  • The block list groups are defined in
    'EC2' => %w[
    ec2_metadata
    ec2_userdata
    ],
  • We probably need to add the cloud.provider fact to both the EC2 and GCE fact groups. Or perhaps we need to block the entire cloud fact, similar to how the operating system group blocks the entire os fact.
  • We're missing an AWS fact group.
@tvpartytonight tvpartytonight added the bug Something isn't working label Mar 19, 2024
@cthorn42 cthorn42 added the accepted Valid issue that we intend to work on when we have the bandwidth label Mar 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accepted Valid issue that we intend to work on when we have the bandwidth bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants