You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All (I think) modules within the collection use the same parameters when determining how and where to address the NetScaler instance:
api_path
nitro_auth_token
nitro_pass
nitro_protocol
nitro_user
nsip
save_config
validate_certs
Given the wide range of modules available, module_defaults is hardly usable, and specifying parameters everywhere is tiresome which makes environment variables the only viable solution (IMO). Registering the modules within an action group would make using module_defaults far easier.
Summary
All (I think) modules within the collection use the same parameters when determining how and where to address the NetScaler instance:
api_path
nitro_auth_token
nitro_pass
nitro_protocol
nitro_user
nsip
save_config
validate_certs
Given the wide range of modules available,
module_defaults
is hardly usable, and specifying parameters everywhere is tiresome which makes environment variables the only viable solution (IMO). Registering the modules within an action group would make usingmodule_defaults
far easier.Action groups aren't documented within the Collection Galaxy metadata structure documentation but within the Module defaults.
Issue Type
Feature Idea
Component Name
Describe alternatives you've considered
The environment variable works just fine, this Feature Request is an enhancement, not a blocker.
Additional Information
The text was updated successfully, but these errors were encountered: