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.

Sign up for GitHub

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

Jump to bottom

Support more fine-grained control when tagging instances for IP publishing #242

Open
1 task
dav3r opened this issue May 15, 2024 · 0 comments
Open
1 task

Support more fine-grained control when tagging instances for IP publishing #242

dav3r opened this issue May 15, 2024 · 0 comments
Labels
improvement This issue or pull request will add or improve functionality, maintainability, or ease of use

Comments

@dav3r
Copy link
Member

dav3r commented May 15, 2024

💡 Summary

From @mcdonnnj in #240 (review):

Allow control over which instances of a given type have their IP information published e.g. I want Windows0 to be private but Windows1 to be published.

Motivation and context

This would increase the flexibility of the egress IP publishing mechanism.

Implementation notes

None

Acceptance criteria

  • One or more operations subnet instances of a specific type can be tagged to have their public IPs published, while one or more other instances of that same type can remain tagged so that their IPs will NOT be published.
@dav3r dav3r added the improvement This issue or pull request will add or improve functionality, maintainability, or ease of use label May 15, 2024
@dav3r dav3r mentioned this issue May 15, 2024
Merged
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
improvement This issue or pull request will add or improve functionality, maintainability, or ease of use
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dav3r