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

Add a type to profiles output for virtual-servers in bigip_device_info module #2396

Open
minsis opened this issue Mar 6, 2024 · 0 comments
Labels
enhancement PRs or Issues for basic feature requests for an existing module. untriaged issue that needs an initial response from the developers

Comments

@minsis
Copy link

minsis commented Mar 6, 2024

Is your feature request related to a problem? Please describe.

We use bigip_device_info to build reports on our virtual servers. One of the things we report on are the profiles associated with it. The problem is the profiles is a list of just generic names with no types. A context of all doesn't tell me anything about the type of profile it actually is.

Describe the solution you'd like

It would be nice to add some of type attribute to define what the profile type actually is (http, oneconnect, etc)

Describe alternatives you've considered

The only other alterntive we have is running a shell script where tmsh show ltm virtual <name> and greping for the specific profiles. For exampe: tmsh show ltm virtual <name> all-properties detail |egrep 'Ltm::OneConnect'

Additional context

Looking at the API calls there is a flag to gather extended info. While the API also does not specify the type of profile it is, it does however list the direct link to said profile which does happen to have the type in it.

{
  "context" : "all",
  "fullPath" : "/Common/http",
  "generation" : 105,
  "kind" : "tm:ltm:virtual:profiles:profilesstate",
  "name" : "http",
  "nameReference" : {
     "link" : "https://localhost/mgmt/tm/ltm/profile/http/~Common~http?ver=17.1.1.1"
  },
  "partition" : "Common",
  "selfLink" : "https://localhost/mgmt/tm/ltm/virtual/~Common~vs_network-lab-nginx-https/profiles/~Common~http?ver=17.1.1.1"
},
{
  "context" : "all",
  "fullPath" : "/Common/tcp",
  "generation" : 105,
  "kind" : "tm:ltm:virtual:profiles:profilesstate",
  "name" : "tcp",
  "nameReference" : {
     "link" : "https://localhost/mgmt/tm/ltm/profile/tcp/~Common~tcp?ver=17.1.1.1"
  },
  "partition" : "Common",
  "selfLink" : "https://localhost/mgmt/tm/ltm/virtual/~Common~vs_network-lab-nginx-https/profiles/~Common~tcp?ver=17.1.1.1"
},
{
  "context" : "all",
  "fullPath" : "/Common/testoneconnect",
  "generation" : 126,
  "kind" : "tm:ltm:virtual:profiles:profilesstate",
  "name" : "testoneconnect",
  "nameReference" : {
     "link" : "https://localhost/mgmt/tm/ltm/profile/one-connect/~Common~testoneconnect?ver=17.1.1.1"
  },
  "partition" : "Common",
  "selfLink" : "https://localhost/mgmt/tm/ltm/virtual/~Common~vs_network-lab-nginx-http/profiles/~Common~testoneconnect?ver=17.1.1.1"
}

The nameReference.link URL has the profile type in the URL: https://localhost/mgmt/tm/ltm/profile/http/~Common~http?ver=17.1.1.1. In this case its an http profile.

@minsis minsis added enhancement PRs or Issues for basic feature requests for an existing module. untriaged issue that needs an initial response from the developers labels Mar 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement PRs or Issues for basic feature requests for an existing module. untriaged issue that needs an initial response from the developers
Projects
None yet
Development

No branches or pull requests

1 participant