Skip to content

feat: add get_instances_by_security_group prompt#103

Merged
paikend merged 4 commits intoopenstack-kr:developfrom
paikend:feat/get-instances-by-security-group
Apr 3, 2026
Merged

feat: add get_instances_by_security_group prompt#103
paikend merged 4 commits intoopenstack-kr:developfrom
paikend:feat/get-instances-by-security-group

Conversation

@paikend
Copy link
Copy Markdown
Collaborator

@paikend paikend commented Apr 1, 2026

Summary

  • Add get_instances_by_security_group prompt that guides LLM to find compute instances associated with a specific security group using existing get_servers tool
  • Enable prompt registration in server.py
  • Add tests for the new prompt

Closes #101

Test plan

  • test_get_instances_by_security_group_prompt_registered — verifies prompt is registered with MCP
  • test_get_instances_by_security_group_prompt_content — verifies prompt returns expected content with security group name
  • All 158 tests pass

Add a prompt that guides LLM to find compute instances associated
with a specific security group using existing tools.

Closes openstack-kr#101
@choieastsea choieastsea self-requested a review April 1, 2026 12:29
Align naming with compute_tools convention (server over instance)
as suggested in code review.
@paikend
Copy link
Copy Markdown
Collaborator Author

paikend commented Apr 2, 2026

동해님 피드백 감사합니다! server로 네이밍 통일하는 게 맞네요 👍 반영 완료했습니다!

Copy link
Copy Markdown
Collaborator

@S0okJu S0okJu left a comment

Choose a reason for hiding this comment

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

첫 프롬프트네요!! 제작해주셔서 감사합니다.

prompt 테스트 코드 폴더 및 파일 구조를 tool과 통일해보면 어떨까요?

Wrap test functions in TestPrompts class and move imports to
module level, matching the pattern used in tests/tools/.
@paikend
Copy link
Copy Markdown
Collaborator Author

paikend commented Apr 2, 2026

감사합니다! 테스트 코드를 tools 쪽과 동일하게 클래스 구조(TestPrompts)로 변경하고, import도 모듈 레벨로 올렸습니다. 반영 완료했습니다 👍

Copy link
Copy Markdown
Collaborator

@S0okJu S0okJu left a comment

Choose a reason for hiding this comment

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

반영해주셔서 감사합니다.

security group은 네트워크 영역인데 tool과 동일하게 test_network_prompts.py 에 저장해두는게 어떨까요?

Align test file naming with tools convention (e.g. test_network_tools.py)
since security group is a network domain feature.
@paikend
Copy link
Copy Markdown
Collaborator Author

paikend commented Apr 3, 2026

감사합니다! test_prompts.py → test_network_prompts.py로 변경했습니다. tools 쪽 네이밍(test_network_tools.py)과 통일! 👍

Copy link
Copy Markdown
Collaborator

@S0okJu S0okJu left a comment

Choose a reason for hiding this comment

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

👍 LGTM

수정해주셔서 감사합니다.

@paikend
Copy link
Copy Markdown
Collaborator Author

paikend commented Apr 3, 2026

혹시 이 PR에 사람 있나요?

@paikend paikend merged commit eba3e6f into openstack-kr:develop Apr 3, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[FEAT] Add get instances associated by security group prompt

3 participants