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

test(e2e): Create multiple GCP targets #5408

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

elimt
Copy link
Member

@elimt elimt commented Jan 5, 2025

Update tests to create 2 GCP instances with different filters to test out discovering GCP instances by filter

Update tests to create 2 GCP instances with different filters to test out discovering GCP instances by filter
@elimt elimt added this to the 0.19.x milestone Jan 5, 2025
@elimt elimt requested a review from moduli January 5, 2025 23:11
@elimt elimt requested a review from a team as a code owner January 5, 2025 23:11
@elimt elimt changed the title test(e2e): Create multiple targets test(e2e): Create multiple GCP targets Jan 6, 2025
johanbrandhorst
johanbrandhorst previously approved these changes Jan 6, 2025
Comment on lines +257 to +258
var targetIps []string
err = json.Unmarshal([]byte(c.GcpHostSetIps1), &targetIps)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just realized, is this being used anywhere?

EDIT: Wait, should all of these expected values be set tot he length of targetIps?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually, I have to take that out because it's not being used

For your second comment, the targetIps are 2. The private IP and the public IP.

When we create a host set with a specific filter that matches Target 1 in this example, only 1 host catalog is created with 2 IP addresses so only 1 HostId will be returned. The assertion only checks for 1 host catalog returned

@elimt elimt added the pr/no-milestone Ignores the Milestone Check label Jan 23, 2025
@elimt elimt removed this from the 0.19.x milestone Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr/no-milestone Ignores the Milestone Check
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants